LSP: ENOENT on Windows — spawn cannot find .cmd shim executables
Resolved 💬 3 comments Opened Apr 1, 2026 by corvo007 Closed May 10, 2026
Description
LSP tool fails on Windows with ENOENT: no such file or directory, uv_spawn 'typescript-language-server'.
Environment
- Windows 11 Pro
- Claude Code latest (CLI)
typescript-lsp@claude-plugins-officialplugin enabledtypescript-language-server@5.1.3installed globally via npm- Binary confirmed in PATH:
C:\Users\...\AppData\Roaming\npm\typescript-language-server.cmd
Steps to Reproduce
- Install
typescript-language-serverglobally on Windows (npm i -g typescript-language-server typescript) - Enable the
typescript-lspplugin - Use the LSP tool on any
.tsfile (e.g., hover, documentSymbol, goToDefinition)
Error
Error performing documentSymbol: ENOENT: no such file or directory, uv_spawn 'typescript-language-server'
Root Cause
On Windows, npm installs global packages as .cmd batch script shims (e.g., typescript-language-server.cmd), not as directly executable binaries.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗