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-official plugin enabled
  • typescript-language-server@5.1.3 installed globally via npm
  • Binary confirmed in PATH: C:\Users\...\AppData\Roaming\npm\typescript-language-server.cmd

Steps to Reproduce

  1. Install typescript-language-server globally on Windows (npm i -g typescript-language-server typescript)
  2. Enable the typescript-lsp plugin
  3. Use the LSP tool on any .ts file (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.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗