Align @types/node with VS Code extension host Node runtime

[SingleSourceStudios]

Context

CodeRabbit flagged during PR #28 review that @types/node@^22.0.0 in editors/vscode/package.json overshoots the Node runtime available in the VS Code extension host for our declared minimum (engines.vscode: ^1.80.0).

VS Code 1.80 ships Node 16.x. VS Code 1.90+ (May 2024) ships Node 20.x. No released VS Code version yet ships Node 22.x, so @types/node@^22 exposes API surface that doesn't exist at runtime.

Why it didn't block v0.1.1

editors/vscode/src/extension.ts is purely declarative — it registers language config, grammars, and snippets via VS Code APIs only. It does not import Node stdlib (fs, path, process, Buffer, etc.), so the type/runtime mismatch has no practical impact on shipped v0.1.1.

Fix

Two viable alignments:

Option A — match current Node 20 host (recommended):

• @types/node: ^22.0.0 → ^20.0.0
• engines.vscode: ^1.80.0 → ^1.90.0

Covers ~99% of active VS Code installs (1.90 is ~2 years old). Allows safe use of Node 20 APIs if we ever add runtime logic (validation CLI integration, schema loading from disk, etc.).

Option B — match legacy Node 16 host (conservative):

• @types/node: ^22.0.0 → ^16.0.0
• Keep engines.vscode: ^1.80.0

Only pick this if we care about users stuck on 3-year-old VS Code. Probably not worth the ceiling on Node API surface.

Acceptance Criteria

• @types/node and engines.vscode are consistent (runtime supports types)
• npm install in editors/vscode/ clean
• npm run esbuild succeeds
• Extension builds and loads in VS Code 1.90+ without warnings
• Ship as part of the next extension release (v0.1.2+)

Out of scope

• This does not affect the root monorepo @types/node alignment (tracked separately in chore(deps): align @types/node with CI Node runtime version #24)
• Extension host Node runtime is independent of the Node version used by @logic-md/core, @logic-md/cli, @logic-md/mcp

References

• CodeRabbit comment on PR chore(vscode): prep extension for Marketplace publish #28 (resolved without action — deferred to this issue)
• VS Code Node version history: Electron 29 update microsoft/vscode#210467
• VS Code extension host API reference: https://code.visualstudio.com/api/references/vscode-api

[traycerai]

Warning

Ticket Assist will be discontinued on May 1, 2026. After that date, the feature will no longer be available. We suggest installing the Traycer IDE Extension for continued AI-powered, spec-driven development. Thank you for choosing Traycer!

Plan

Observations

The workspace snapshot does not include editors/vscode/ (it is tracked separately from the root monorepo). The root package.json correctly pins @types/node@^22 and engines.node: >=22.0.0 for the monorepo packages — those are not in scope here (tracked in #24). The issue targets only editors/vscode/package.json, where @types/node@^22.0.0 overshoots the Node runtime bundled in the VS Code extension host.

Approach

Apply Option A from the issue: bump engines.vscode to ^1.90.0 and downgrade @types/node to ^20.0.0. VS Code 1.90 ships Node 20.x, making types and runtime consistent. VS Code 1.90 is ~2 years old, covering ~99% of active installs, and Node 20 API surface is sufficient for any foreseeable extension logic.

---

Implementation Steps

1. Update editors/vscode/package.json

Make two targeted changes:

• engines.vscode: change ^1.80.0 → ^1.90.0
• devDependencies["@types/node"]: change ^22.0.0 → ^20.0.0

2. Regenerate the lock file

Inside editors/vscode/, run npm install. This removes the @types/node@22.x resolution and installs the latest @types/node@20.x release, updating package-lock.json accordingly.

3. Verify the build

Run npm run esbuild (or the equivalent compile script) inside editors/vscode/ to confirm the extension still compiles cleanly with the updated types.

4. Update CHANGELOG.md / release notes

Record the change under the upcoming v0.1.2 entry:

• Aligned @types/node (^20.0.0) with the VS Code 1.90+ extension host Node 20 runtime.
• Raised minimum VS Code engine requirement to ^1.90.0.

---

Consistency check

Field	Before	After
engines.vscode	^1.80.0	^1.90.0
@types/node	^22.0.0	^20.0.0
Actual host Node	16.x (1.80)	20.x (1.90+)

No changes are needed in the root monorepo package.json or any packages/* — those are governed by #24.

Import In IDE

🤖 Prompt for AI Agents

## Observations

The workspace snapshot does not include `editors/vscode/` (it is tracked separately from the root monorepo). The root `package.json` correctly pins `@types/node@^22` and `engines.node: >=22.0.0` for the monorepo packages — those are **not** in scope here (tracked in #24). The issue targets only `editors/vscode/package.json`, where `@types/node@^22.0.0` overshoots the Node runtime bundled in the VS Code extension host.

## Approach

Apply **Option A** from the issue: bump `engines.vscode` to `^1.90.0` and downgrade `@types/node` to `^20.0.0`. VS Code 1.90 ships Node 20.x, making types and runtime consistent. VS Code 1.90 is ~2 years old, covering ~99% of active installs, and Node 20 API surface is sufficient for any foreseeable extension logic.

---

## Implementation Steps

### 1. Update `editors/vscode/package.json`

Make two targeted changes:

- **`engines.vscode`**: change `^1.80.0` → `^1.90.0`
- **`devDependencies["@types/node"]`**: change `^22.0.0` → `^20.0.0`

### 2. Regenerate the lock file

Inside `editors/vscode/`, run `npm install`. This removes the `@types/node@22.x` resolution and installs the latest `@types/node@20.x` release, updating `package-lock.json` accordingly.

### 3. Verify the build

Run `npm run esbuild` (or the equivalent compile script) inside `editors/vscode/` to confirm the extension still compiles cleanly with the updated types.

### 4. Update `CHANGELOG.md` / release notes

Record the change under the upcoming `v0.1.2` entry:
- Aligned `@types/node` (`^20.0.0`) with the VS Code 1.90+ extension host Node 20 runtime.
- Raised minimum VS Code engine requirement to `^1.90.0`.

---

### Consistency check

| Field | Before | After |
|---|---|---|
| `engines.vscode` | `^1.80.0` | `^1.90.0` |
| `@types/node` | `^22.0.0` | `^20.0.0` |
| Actual host Node | 16.x (1.80) | 20.x (1.90+) |

No changes are needed in the root monorepo `package.json` or any `packages/*` — those are governed by #24.

---

Execution Information

Branch: main
Commit: 8c83e18

---

💡 Tips

Supported Commands (Inside Comments)

• Use @traycerai generate to iterate on the previous version of the implementation plan.

Supported Commands (Inside Description)

• Add @traycerai ignore anywhere in the ticket description to prevent this ticket from being processed.
• Add @traycerai branch:<branch-name> anywhere in the ticket description to specify the target branch for the implementation plan.

Community

• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[SingleSourceStudios]

PR #30 is a concrete instance of this: Dependabot tried to bump @types/node → 24 while engines.node stays on 22. Closed it, and added a version-update:semver-major ignore rule to .github/dependabot.yml for @types/node in both / and /editors/vscode so the same PR doesn't auto-reopen.