Repository navigation
chore(deps): replace deprecated vsce with @vscode/vsce - #22
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves the extension packaging tool from
vsce, which was renamed and is deprecated, to@vscode/vsce4.0.0, the same CLI under its current name. Thevscecommand stays the same, sonpm run packageand the publish workflow need no change.@vscode/vsceno longer accepts both a.vscodeignoreand afilesfield inpackage.json, so.vscodeignoreis removed and thefileslist (already the npm package's contents) now decides what goes into the.vsixtoo.What was done
package.json:vsce ^2.15.0→@vscode/vsce ^4.0.0(latest stable, out since 2026-09-14, so past the repo's 7-day Dependabot cooldown). It needs Node 22 or later; CI and the publish workflow already run Node 22.package-lock.json: regenerated bynpm uninstall vsceandnpm install -D @vscode/vsce@^4.0.0. Every changed package is in the packaging tool's own tree (or shared with nodemon, which still resolves within its ranges); all from registry.npmjs.org..vscodeignoreremoved. With 4.0.0vsce packagestops with "Both a .vscodeignore file and a "files" property in package.json were found". Keeping.vscodeignorewould mean droppingfiles, which is the npm package's API, sofilesstays. The.vsixnow holdspackage.json,index.js,index.d.ts,themes/*.json,icon.png,README.mdandLICENSE.md(12 entries, 186 KB). Before, it also carriedsrc/,tsconfig.json,DISPLAY-P3.mdandcolor-comparison.html(20 entries, 205 KB), none of which the extension reads. The README's images are already absolute URLs, so the Marketplace page renders the same.npm ci,npx tsc --noEmit,npm testandnpm run packageall pass; the generatedthemes/*.jsonare unchanged.vsce publishitself (needs the Marketplace token).--patis still a documented option ofvsce publishin 4.0.0, and so is theVSCE_PATvariable.How to review
npm ci && npm run build && npm run package, thenunzip -l bootstrap-vscode-theme-0.0.10.vsix: 12 entries, withthemes/andicon.png.🤖 Generated with Claude Code