Why you should not use npm start for applications with child processes

Hey guys, I wrote this post about the famous npm start command and why it should not be used when you are managing child processes in your app. Basically, it all boils down in case of a FATAL failure or the process being killed with SIGINT signal (CTRL+C) which is not being properly passed to child processes when using npm start. This means, when you are listening for the SIGINT signal in your child process in order to enable cleanup/exit gracefully, this signal won't be received in the child process. You can find the article at the Lisk blog.

Submitted May 21, 2019 at 10:13AM by thenoisywatcher