From 296ea887dc2d68e4decaeb2d265bad6d84ac7a84 Mon Sep 17 00:00:00 2001 From: kkdev92 <112151103+kkdev92@users.noreply.github.com> Date: Sun, 30 Aug 2026 01:05:16 +0900 Subject: [PATCH] docs(migration): point the manifest step at the command line and contributed: false The guide was written before `vscode-ext-kit manifest` and `defineSettings({ contributed: false })` landed, so its manifest step only named the test. Both are on main now; the step says so. Co-Authored-By: Claude Fable 5 --- docs/migration-from-2x.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/docs/migration-from-2x.md b/docs/migration-from-2x.md index 9332225..df3d9e1 100644 --- a/docs/migration-from-2x.md +++ b/docs/migration-from-2x.md @@ -315,8 +315,15 @@ honest](guide.md#keeping-packagejson-honest) has the test. Run it now: a migration that renamed a section or fixed a default is exactly when the two drift. -`npx vscode-ext-kit plan ./dist/extension.js --check` is the same idea one level -up — preflight, from the command line, against the built entry. +The same comparison is available without writing the test: +`npx vscode-ext-kit manifest ./dist/extension.js` reports every disagreement +between the built entry's plan and `package.json`, and `--apply` adds the +commands and settings the manifest is missing, with placeholder titles and +descriptions for a person to replace. A section the extension only reads — +`editor`, say — is declared with `contributed: false`, so neither check asks the +manifest for it. `npx vscode-ext-kit plan ./dist/extension.js --check` is the +same idea one level up: preflight, from the command line, against the built +entry. ## 9. Add an Extension Host lane