You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2021. It is now read-only.
Hey,
I am trying to handle signals in my application and they may come multiple times.
I found here that the signal is propagated only the first time (the second signal will kill npm process and won't pass it to the child). In some use cases, we want to actually receive the second signal as well.
I also found this post talking to something very similar. In the end, they replaced the npm run start command of with node index.js. Is this what npm suggest as best practice in that case?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey,
I am trying to handle signals in my application and they may come multiple times.
I found here that the signal is propagated only the first time (the second signal will kill npm process and won't pass it to the child). In some use cases, we want to actually receive the second signal as well.
I also found this post talking to something very similar. In the end, they replaced the
npm run start
command of withnode index.js
. Is this what npm suggest as best practice in that case?The text was updated successfully, but these errors were encountered: