tsx watch in concurrently hangs on Windows if there are certain modules imports

[NadAlaba]

Acknowledgements

• I read the documentation and searched existing issues to avoid duplicates
• I understand this is a bug tracker and anything other than a proven bug will be closed
• I understand this is a free project and relies on community contributions
• I read and understood the Contribution guide

Minimal reproduction URL

https://github.com/NadAlaba/tsx-issue-repro

Problem & expected behavior (under 200 words)

• Running tsx watch index.ts inside concurrently on Windows makes tsx watch hang, without running the ts file, if the ts file has references to a suspicious module.
• Currently discovered suspicious modules are: chalk, prom-client, swagger-stats, googleapis.
• This issue is almost certainly not a concurrently issue because it happens without concurrently as was discovered on this turbo issue.

Bugs are expected to be fixed by those affected by it

• I'm interested in working on this issue

Compensating engineering work will speed up resolution and support the project

• I'm willing to offer $10 for financial support

[privatenumber]

This issue is almost certainly not a concurrently issue because it happens without concurrently as was discovered on this vercel/turborepo#7834.

Can you remove concurrently from your minimal reproduction then?

Can you also add a GitHub Action that reproduces the bug on Windows? I don't have a Windows

[NadAlaba]

Can you remove concurrently from your minimal reproduction then?

@privatenumber As far as I can tell this issue requires tsx watch to run through concurrently or turbo in order to happen. I was saying it happened without concurrently, but with turbo on the linked issue.

Can you also add a GitHub Action that reproduces the bug on Windows? I don't have a Windows

Done!

[iuroc]

This issue is caused by import/require "process" combined with process.stdin.on("data", ()=>{}).

tsx/src/watch/index.ts

Line 219 in bd83d3b

process.stdin.on('data', () => reRun('Return key'));

You can add the -r option to concurrently to resolve it.

Disabling OnReturnKey can also solve the issue.

I have submitted a PR (#639) that allows you to manually disable OnReturnKey by using --on-return-key=false.