Exit with 130 after receiving SIGINT

[isaacl]

pnpm should exit with non-zero code when aborting
abnormally due to SIGINT

Fixes: pnpm/pnpm#9626

[isaacl]

I pushed an update, which should fix the tests

[zkochan]

Does this work the same in npm CLI? Can you verify by finding the related code in npm CLI?

[isaacl]

@zkochan re: npm behavior

Well ... this PR makes the behavior closer. Right now, in the most common case -- Ctrl-C in an interactive shell -- npm exits with 130, while pnpm exits with 0.

$ npm run sleep &>/dev/null &; sleep .5; kill -INT %1; wait $!; echo $?
130
$ pnpm run sleep &>/dev/null &; sleep .5; kill -INT %1; wait $!; echo $?
0

While npm is running a script, it captures SIGINT and relays to children, similar to pnpm.

npm does not track when its traps activate.

But, if a child dies by signal -- npm sends this signal to self (run-script-pkg.js) (pnpm does this too ... but not with SIGINT).

If the goal is purely consistency with NPM, one could simply roll back #41

[zkochan]

In that case maybe we should roll back #41

[isaacl]

In that case maybe we should roll back #41

Yes, agreed. I've moved the small other suggestions to #51

---

BTW: this origin of this issue is from a project I work on that has package.json scripts like pnpm run test:ct && pnpm run test:e2e. Hitting Ctrl-C does not abort as expected because the first pnpm instance exits with 0.