Improper handling of graceful exits (same as #95)

[greguz]

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/greguz/tsx-issue

Problem & expected behavior (under 200 words)

My env:

• Node.js v22.13.0
• macOS 15.3.2 (24D81) (Apple M2 Pro)
• tsx v4.19.3

Using the same code from #95 I can constantly trigger a double SIGINT with tsx (clean Node.js works).

console.log('starting up')

process.on('SIGINT', () => {
  console.log('shutting down')

  // simulate cleanup
  setTimeout(() => {
    console.log('cleanly exiting')
    process.exit(0)
  }, 5000)
})

// run forever
setInterval(() => {}, 1 << 30)

╭─greguz@prunix ~/Development/bug ‹master●› 
╰─$ npx tsx z.ts      
starting up
^Cshutting down
shutting down
cleanly exiting
╭─greguz@prunix ~/Development/bug ‹master●› 
╰─$ node z.js   
starting up
^Cshutting down
cleanly exiting

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]

Does this still happen if you run tsx directly, without npx?

[greguz]

That was unexpected! Is this behavior supposed to happen?

╭─greguz@prunix ~/Development/greguz/tsx-issue ‹master●› 
╰─$ ./node_modules/.bin/tsx z.ts 
starting up
^Cshutting down
cleanly exiting
╭─greguz@prunix ~/Development/greguz/tsx-issue ‹master●› 
╰─$ npx tsx z.ts
starting up
^Cshutting down
shutting down
cleanly exiting

[privatenumber]

I'm not sure 🤷‍♂️

You can report it to npx as that's the layer that's not handling your signal.

[privatenumber]

FYI I dont think this has anything to do with tsx.

You can likely reproduce with npx node z.js

[greguz]

Thank you for the fast support. I opened an issue to the npm project. I let you known how comes in the future 🙃

PS: this was a nasty bug for me, because the double SIGINT paired with close-with-grace kills the process instantly (and my poor AMQP connection is not happy about it).

[privatenumber]

Yeah, I saw and I was responding to that indirectly.

Typically, issues require minimal reproductions, and your reproduction in npm/cli#8164 is technically not minimal because it can be reproduced without tsx.

It saves the maintainer time to keep the report slim and makes it obvious where the problem is.

[greguz]

You are absolutely right. I'll update the issue.