How to solve the problem of frequent manual restart after node modification

This time I will introduce to you how to solve the problem of frequent manual restart after node modification. What are the precautions to solve the problem of frequent manual restart after node modification. The following is a practical case, let's take a look.

During the development process, every time after modifying the code and saving it, we need to manually restart the program to see the effect of the changes. This tedious problem can be solved by using supervisor, global installation supervisor:

npm install -g supervisor

Run supervisor --harmony server startup program, as shown below:

supervisor will monitor the files with node and js suffixes in the current directory. When these files are changed, supervisor will automatically restart the program.

I believe you have mastered the method after reading the case in this article. For more exciting information, please pay attention to other related articles on the php Chinese website!

Recommended reading:

detailed explanation of steps for using nodeJs crawler

vscode debugging and compiled js code step analysis

The above is the detailed content of How to solve the problem of frequent manual restart after node modification. For more information, please follow other related articles on the PHP Chinese website!