Bug
apps/lsp/build.ts:20 lists an asset that doesn't exist:
{ from: ['./src/run.js'], to: '../vscode/out/lsp' },apps/lsp/src/run.js isn't in the repo, and nothing else references run.js. esbuild-plugin-copy silently copies nothing for an unmatched glob, so the build still succeeds. It's dead config, left over from an earlier layout.
Fix
Delete that line. Then confirm that yarn build-vscode still produces apps/vscode/out/lsp/lsp.js and that the extension starts the language server (serverModule in apps/vscode/src/lsp/client.ts points at lsp.js, not run.js).
Low priority, but it's misleading when you're reading the build, and it'll cause a warning or error if the copy plugin ever gets stricter about unmatched globs (relevant to the esbuild upgrade).
Found during the dependency-upgrade research.
Bug
apps/lsp/build.ts:20lists an asset that doesn't exist:apps/lsp/src/run.jsisn't in the repo, and nothing else referencesrun.js.esbuild-plugin-copysilently copies nothing for an unmatched glob, so the build still succeeds. It's dead config, left over from an earlier layout.Fix
Delete that line. Then confirm that
yarn build-vscodestill producesapps/vscode/out/lsp/lsp.jsand that the extension starts the language server (serverModuleinapps/vscode/src/lsp/client.tspoints atlsp.js, notrun.js).Low priority, but it's misleading when you're reading the build, and it'll cause a warning or error if the copy plugin ever gets stricter about unmatched globs (relevant to the esbuild upgrade).
Found during the dependency-upgrade research.