From 41fbc81b0947193a8ce1cccb872ef75837266704 Mon Sep 17 00:00:00 2001 From: Arina Neshlyaeva Date: Wed, 30 Sep 2026 15:17:39 -0700 Subject: [PATCH] Add explicit `types: ["node"]` to tsconfig MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit TypeScript emits `Cannot find name 'path'/'net'/'process'` when compiling `extension.ts` against `vscode-languageclient@10.x` (see #154's failing CI). The messages come with TS's own remedy: "add 'node' to the types field in your tsconfig". The v9 → v10 upgrade drops a transitive that used to trigger auto-inclusion of `@types/node`; declaring `types: ["node"]` explicitly loads `@types/node` regardless. `@types/vscode` is imported by module path and doesn't need to appear in `types`, so IntelliSense on `vscode` APIs is unaffected. Co-Authored-By: Claude Opus 4.7 (1M context) --- client-vscode/tsconfig.json | 1 + 1 file changed, 1 insertion(+) diff --git a/client-vscode/tsconfig.json b/client-vscode/tsconfig.json index ad1837f..0644bcc 100644 --- a/client-vscode/tsconfig.json +++ b/client-vscode/tsconfig.json @@ -5,6 +5,7 @@ "moduleResolution": "Node16", "outDir": "out", "lib": ["es2016"], + "types": ["node"], "sourceMap": true, "skipLibCheck": true },