How do you restart your local node.js server when developing?

Question

Node.js

When writing javascript for the browser, you can save the file at any time, switch to the browser and press f5. The new code will be uploaded and can be tested.
When writing in node.js, the code update chain is longer: first you need to switch to the console, stop the server, start the server, go to the browser, press f5.
After the 50th time in a day, it gets very annoying. So I'm wondering how do those who have some development experience with node.js deal with this problem? Are you setting the IDE to restart the server on the build command?
For example, in Django there is no such problem at all, where the development server monitors changes in the source code and automatically restarts itself. And the same php is broadcast on every request.

Answer 1

there are many node restarters, for example, when changing the project code. but usually it is inconvenient

Answer 2

Well, personally, I use the following key combination in the console:

ctrl+c
arrowUp
enter

I'm sure you can make it much more convenient, incl. as suggested by VBart

Answer 3

In KDE, it can be easily hung up on a hotkey or a mouse gesture.

Answer 4

You can write a simple daemon that checks the files in the directory, and if something changes, it restarts the server.

Answer 5

I wrote a simple starter.js that hangs in the console (it also respawns the process of the application itself in case of an error).
I kill ctrl + c, allowUp, enter - as TheShock wrote above.
In the case when I write and debug a single script, I use the cloud9 IDE and run the script through the IDE itself (there is both launch and console output).

Answer 6

Of the restarters (of which there are really a lot), this one was the most convenient for me to use: github.com/lrbabe/node-DJs , because it looks not just for files in some folder, but for changes in the source code.

Answer 7

It's like debugging nginx, sorry ))

Answer 8

The Impress application server implements tracking of files that are loaded into via require. When they change, without reloading the project, the old one is removed from memory and a new one is loaded.

Answer 9

I am using nodemon.
nodemon app.js