[QUESTION] NPM Scripts double SIGINT with CTRL+C - is this intentional?

[kellyjandrews]

What / Why

I've run into some issues recently where running a node process using an npm script and using CTRL+C to exit will fire the command twice. It's something I had not encountered before, but unsure if this is intentional with npm scripts, or actually considered a bug.

Where

This happened specifically with regard to the Firebase CLI. I filed an issue here - firebase/firebase-tools#2507

i  emulators: Received SIGINT (Ctrl-C) for the first time. Starting a clean shutdown.
i  emulators: Please wait for a clean shutdown or send the SIGINT (Ctrl-C) signal again to stop right now.
i  Automatically exporting data using --export-on-exit "./data" please wait for the export to finish...

⚠  emulators: Received SIGINT (Ctrl-C) 2 times. You have forced the Emulator Suite to exit without waiting for 2 subprocesses to finish. These processes may still be running on your machine:

I have tested this multiple times, and it is not a keyboard error or mistyped - just get's sent twice.

Who

• n/a

References

• n/a

[darcyclarke]

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.