[BUG] typescript-lsp plugin fails on Windows: uv_spawn cannot execute .cmd wrappers

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Platform: Windows 11 Enterprise (10.0.22621)
Claude Code version: (current)
Plugin: typescript-lsp@claude-plugins-official v1.0.0

Problem

/doctor reports:

Plugin (plugin:typescript-lsp:typescript): ENOENT: no such file or directory, uv_spawn 'typescript-language-server'

Root cause

typescript-language-server is correctly installed globally via npm (v5.3.0).
On Windows, npm global installs create three wrapper files — none of which are a
native .exe:

• typescript-language-server → bash script (#!/bin/sh)
• typescript-language-server.cmd → CMD wrapper (requires cmd.exe /c)
• typescript-language-server.ps1 → PowerShell wrapper

Claude Code's process spawner (uv_spawn / libuv) looks for a native Windows
executable. It does not invoke cmd.exe automatically for .cmd wrappers, so
all three variants fail to spawn.

Both user and system PATH include C:\nvm4w\nodejs (nvm for Windows).

Expected behaviour

The plugin should detect Windows and spawn via
cmd.exe /c typescript-language-server.cmd --stdio
(analogous to how VS Code's LSP client handles this on Windows).

Workaround

None available without a native .exe shim or a plugin-side settings key to
override the spawn command.

What Should Happen?

Claude should solve this issue

Error Messages/Logs

Steps to Reproduce

see above

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.177

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_