nodemon: stuck on "restarting due to changes" after file change

  • nodemon -v: 1.18.6
  • node -v: 11.2.0
  • Operating system/terminal environment: Windows 10 / PowerShell and Cmd Prompt
  • Command you ran: npm start (where “start” : “nodemon app”)

Expected behaviour

After detecting changes, nodemon should kill the current process and execute a new one.

Actual behaviour

Nodemon detects the changes but fails to actually restart the program. Additionally, every change made to my file produces two lines indicating that the change has been recognized. The following is the output after running npm start and changing the file exactly once:

[nodemon] starting `node app.js`
hello cruel world
[nodemon] restarting due to changes...
[nodemon] restarting due to changes...

If the process exits on its own, nodemon has no issue restarting after a change. It is only an issue if the process is still executing while the changes are detected.

I tried running nodemon locally and globally as well as reinstalling node and npm entirely.

Steps to reproduce

Here is the simplest application to reproduce the problem:

console.log("hello cruel world");
while(true) {};

If applicable, please append the --dump flag on your command and include the output here ensuring to remove any sensitive/personal details or tokens.

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 8
  • Comments: 21 (3 by maintainers)

Most upvoted comments

Still issue (annoying) in Windows