Can't start inspector proxy server in Windows unless I change the dev command to use node --import tsx

[olaservo]

Describe the bug
When I run the command npm run dev to start both the inspector client and server, the client starts but not the proxy server. No errors are logged but when I load the UI it can't connect to the proxy server to get the config from the config endpoint. I can start the server by changing the command to start the server from tsx watch --clear-screen=false src/index.ts to node --import tsx --watch --watch-preserve-output src/index.ts.

To Reproduce
My setup: I am using Windows 10 and node version v22.4.0, npm version 10.8.1, running the terminal in VSCode using a Powershell terminal.

1. Clone inspector locally, run npm install then npm run dev. Open the UI and there will be errors in the console about connection refused when trying to use the config endpoint.

When I try to make a request directly to the server it doesn't appear to be running, unless I run alternate commands to start it.

Expected behavior
Proxy server should start successfully when running npm run dev.

Logs

No proxy server logs are displayed in the terminal, just client app logs. I see connection refused errors in the console when I open the UI because the proxy server isn't running.

Additional context

This might be platform specific, since it happens on 2 of my Windows machines but not my Macbook.