Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SIGINT results in a forced exit every time when running tsx watch with npm #586

Open
4 of 6 tasks
jabrks opened this issue Jun 12, 2024 · 0 comments
Open
4 of 6 tasks
Labels
bug Something isn't working pending triage

Comments

@jabrks
Copy link

jabrks commented Jun 12, 2024

Acknowledgements

  • I read the documentation and searched existing issues to avoid duplicates
  • I am reporting a confirmed bug (not seek debugging help)
  • I understand this is a collaborative project and relies on my contributions
  • I read and understood the Contribution guide

Minimal reproduction URL

https://github.com/jabrks/tsx-reproduction

Problem & expected behavior (under 200 words)

Using npm to run tsx watch results in the following error each time the process is interrupted

[tsx] Previous process hasn't exited yet. Force killing...

The GitHub action in the reproduction linked above demonstrates this by artificially exiting the process after 3 seconds. npm's signal handling behaviour was changed in v10.3.0 as a result of npm/run-script#188 which seems to be related

Bugs are expected to be fixed by those affected by it

  • I'm interested in working on this issue

Compensating engineering work financially will speed up resolution

  • I'm willing to offer financial support
@jabrks jabrks added bug Something isn't working pending triage labels Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working pending triage
Projects
None yet
Development

No branches or pull requests

1 participant