From b216250e4cfd422ee660930e23c51ea96d393b6b Mon Sep 17 00:00:00 2001
From: hyperpolymath <6759885+hyperpolymath@users.noreply.github.com>
Date: Mon, 18 May 2026 11:36:05 +0100
Subject: [PATCH] chore(vscode-ext): migrate vsce -> @vscode/vsce; correct
 build status
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

`vsce` 2.15.0 (the deprecated package) predates `.cjs`-entrypoint
support, so `vsce package` failed looking for `src/index.cjs.js`.
Migrated devDependency to the renamed, maintained `@vscode/vsce` ^3.2.0
(same `vsce` binary, so the `package` script is unchanged).

Also corrected the README "Status" block, which #58 left stale: the
extension DOES compile and the affinescript Vscode stdlib bindings DO
type-check on affinescript main (#35 P2 effectively complete) — the only
real bug was my-lang's own extension.affine (fixed in #60). Documented
that packaging needs a registry-reachable env (WSL npm is unreachable
here, so package/publish must run on CI or a non-WSL host) and that
`.vsix` packaging needs no Azure PAT (only `vsce publish` does).

Refs affinescript#35

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---
 vscode-extension/README.md    | 22 ++++++++++++++--------
 vscode-extension/package.json |  2 +-
 2 files changed, 15 insertions(+), 9 deletions(-)

diff --git a/vscode-extension/README.md b/vscode-extension/README.md
index 726d9df..5921253 100644
--- a/vscode-extension/README.md
+++ b/vscode-extension/README.md
@@ -58,19 +58,25 @@ committed last-good build. Recompiling from the AffineScript source requires:
 
 ```bash
 cd vscode-extension
-npm install
+npm install               # needs a reachable npm registry (NOT WSL here)
 export AFFINESCRIPT_STDLIB=/path/to/affinescript/stdlib
 npm run compile           # affinescript compile --vscode-extension …
-npm run package           # vsce package  -> my-lang-<version>.vsix (no PAT)
+npm run package           # @vscode/vsce package -> my-lang-<version>.vsix
 code --install-extension my-lang-0.3.0.vsix
 ```
 
-> **Status:** the `src/extension.affine` → `out/extension.cjs` recompile is
-> gated on upstream **affinescript#35 Phase 2** (vscode-API stdlib bindings;
-> `stdlib/Vscode.affine` does not yet type-check). Until that lands, the
-> committed `out/extension.cjs` + `src/index.cjs` are the working artifacts;
-> `vsce package` produces an installable `.vsix` from them and needs **no**
-> Azure Marketplace PAT (only `vsce publish` does).
+> **Status:** `src/extension.affine` **compiles** (`affinescript compile
+> --vscode-extension`) and the upstream `stdlib/Vscode.affine` /
+> `VscodeLanguageClient.affine` bindings type-check on affinescript `main`
+> (#35 Phase 2 effectively complete). `src/index.cjs` (the `main`) +
+> `out/extension.cjs` are the runtime artifacts.
+>
+> **Packaging** needs `@vscode/vsce` (the old deprecated `vsce` 2.x cannot
+> handle a `.cjs` entrypoint — it looks for `index.cjs.js`) **and** a
+> registry-reachable environment for `npm install` (the WSL dev box's npm
+> registry is unreachable, so package/publish must run elsewhere — CI or a
+> non-WSL host). `vsce package` → `.vsix` needs **no** Azure Marketplace
+> PAT; only `vsce publish` (Marketplace upload) does.
 
 ## License
 
diff --git a/vscode-extension/package.json b/vscode-extension/package.json
index db2e648..4bcbe1c 100644
--- a/vscode-extension/package.json
+++ b/vscode-extension/package.json
@@ -81,7 +81,7 @@
     "package": "vsce package"
   },
   "devDependencies": {
-    "vsce": "^2.15.0"
+    "@vscode/vsce": "^3.2.0"
   },
   "dependencies": {
     "vscode-languageclient": "^9.0.1"