Bug running NodeJS API on Windows and WSL

[gtoro98]

Verify canary release

• I verified that the issue exists in the latest Turborepo canary release.

Link to code that reproduces this issue

https://github.com/gtoro98/turbo_issue

What package manager are you using / does the bug impact?

npm

What operating system are you using?

Windows

Which canary version will you have in your reproduction?

1.13.1-canary.2

Describe the Bug

NodeJS Fastify server fails to run locally from turborepo on windows systems

Expected Behavior

Server to start

To Reproduce

run npm run dev on issue repo

Additional context

Version 1.12 works fine, this issue only appears to happen on Windows, no problem on M chip macs. Tested with WSL with Ubuntu distro and issue also happens

[chris-olszewski]

Can you include how it is failing? The repro you provided seems to be working fine on my Windows machine:

Information such as which console you are running from and Windows build version could also help.

[gtoro98]

Can you include how it is failing? The repro you provided seems to be working fine on my Windows machine:

Information such as which console you are running from and Windows build version could also help.

It looks like it is running but none of the commands are excecuting and the server isn't running

[tknickman]

@gtoro98 could you also provide the console you're using as well as your windows build version?

Thanks!

[chris-olszewski]

@gtoro98

Can you also confirm if issue is present when directly invoking npm dev in the directory for @armi-pay/api?

[gtoro98]

@tknickman OS Build 22631.3296 but have reproduced in various others on windows powershell, command prompt and terminal

[gtoro98]

@chris-olszewski running 'npm run dev' from within the apps/api directory results in succesful starting of the server

[chris-olszewski]

Closing in favor of #7834 as I believe this is an bad interaction with turbo and tsx on Windows.