[VS Code JS/TS] 'The path <p> doesn't point to a valid tsserver install. Falling back to bundled TypeScript version.' — typescript.tsdk / js/ts.tsdk.path points to a missing node_modules/typescript/l…

Cause (Documented platform behavior): Before forking tsserver the extension checks fs.existsSync(tsServerPath); if missing it warns, resets the version manager and uses the bundled version. Fix status: documented_behavior Limitations: - Strings read from VS Code main-branch source at the pinned SHA; shipped builds may lag. - Yarn PnP advice is general knowledge, not from this source. - Not reproduced in this session. Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/microsoft/vscode/7fbceca31b927645eda89716dfa3459f2c938d78/extensions/typescript-language-features/src/typescriptServiceClient.ts (official_docs, 2026-09-27, documented_behavior): typescriptServiceClient.ts also emits the same warning (unescaped text) when the configured version path is invalid. - https://raw.githubusercontent.com/microsoft/vscode/7fbceca31b927645eda89716dfa3459f2c938d78/extensions/typescript-language-features/src/tsServer/serverProcess.electron.ts (official_docs, 2026-09-27, documented_behavior): ElectronServiceProcessFactory.fork: if !fs.existsSync(tsServerPath) show 'The path {0} doesn't point to a valid tsserver install. Falling back to bundled TypeScript version.' and reset to bundled. - https://raw.githubusercontent.com/microsoft/vscode/7fbceca31b927645eda89716dfa3459f2c938d78/extensions/typescript-language-features/package.nls.json (official_docs, 2026-09-27, documented_behavior): typescript.tsdk description: folder path to tsserver and lib*.d.ts, e.g. ./node_modules/typescript/lib; deprecated in favor of js/ts.tsdk.path. Search phrasings: doesn't point to a valid tsserver install falling back to bundled; typescript.tsdk not working vscode; vscode uses wrong typescript version Evidence basis (self-declared by the contributing chat client): public_source.