Running in dev mode broken on Windows

[olaservo]

Describe the bug
Running npm run dev:windows no longer starts the app successfully.

To Reproduce
On a Windows machine, run npm run dev:windows

Expected behavior
Inspector starts and opens.

Logs
After running the command, this is as far as it gets:

> @modelcontextprotocol/inspector@0.14.3 dev:windows
> node client/bin/start.js --dev

Starting MCP inspector in development mode...

Additional context
Looks like this PR might have introduced this issue? #513

[olaservo]

Update after trying to debug again locally this morning: the Windows-specific stdin: 'ignore' checks in client/bin/start.js might now prevent the spawn processes from working correctly. Temporarily removing these checks seems to allow dev mode to start successfully. We may need to remove the Windows stdin handling entirely if something changed in Vite to solve the original issue.

[darena-mhaque]

Has this not been corrected? I am seeing that the ticket is closed, but the code still exists in start.js:

  if (isWindows) {
    spawnOptions.stdin = "ignore";
  }

I also see that if I remove these lines, I can debug normally, whereas keeping these lines just stops the shell.