This article was first published on Lisk Blog - Medium
You shouldn’t start applications through npm when you have child processes natively supported by Node.js. In this article, we will provide a list of best practices for Node.js applications with a code snippet that outlines the core problem and shows you how to reproduce the issue in 3 steps. In short, we stopped using npm start to run our blockchain’s core and instead opted for using the native node command.
Introduction to npm and its most well-known command ‘npm start’.
Our challenge: npm runs app.js files as a child process of npm.
However, what many don’t know is that while using npm start to trigger node app.js, npm is actually running your app.js file as a child process of npm which manages this. In 99% of the cases, you should just don’t care about this, but things can get tricky when working with child processes in your own project. Can you feel the inception happening here? #child-process-inception
To give you a better understanding of how this is relevant to our “npm vs node” problem, let’s talk about how we are running Lisk Core. For those who don’t know what Lisk Core is, essentially, it is a program that implements ...
To keep reading, please go to the original article at:
Lisk Blog - Medium