Nodemon stuck at "restarting due to changes..." and won't restart the server

nodemon not restarting
nodemon alternative
nodemon stop
nodemon ignore directory
nodemon execute command
chokidar vs nodemon
nodemon environment variables
nodemon dev install

I have a pretty basic nodemon configuration. I'm fixing this legacy node 7 project that I inherited and trying to make the development process a little bit painful. First thing first, a proper restart-and-transpile process (since it's built using ES6 modules syntax).

This is my folder structure:

- src
  |- index.js
- dist
  |- index.js
- index.js
- nodemon.js

I run nodemon as "start:dev": "nodemon index.js"

Here's it's content:

// index.js
if (process.env.NODE_ENV === 'production') {
  require('./dist/index.js');
} else {
  require('babel-register')({});
  require('babel-polyfill');
  require('./src/index.js');
}

The idea is that the code is transpiled on runtime, so that I don't have to stop server, re-transpile, start server manually, as I have been doing before.

Last but not least, nodemon config

// nodemon.js
{
  "restartable": "rs",
  "ignore": [
    ".git",
    "node_modules/**/node_modules"
  ],
  "verbose": true,
  "watch": [
    "src"
  ],
  "env": {
    "NODE_ENV": "development"
  },
  "ext": "js json"
}

I took this setup from MERN, and I think it should work. However, when I made a change and save, it goes:

[nodemon] files triggering change check: src/index.js
[nodemon] matched rule: /Users/me/project/path/src/**/*
[nodemon] changes after filters (before/after): 1/1
[nodemon] restarting due to changes...
[nodemon] src/index.js

(stuck here. it never restarts)

I've been checking the code, and the only thing that I'm unfamiliar with, that maybe be causing it I can think of would be a child_process.execFileSync() call, that will call a java tool; and a connection pool with mysql.createPool() (mysql package).

Tried both in Node 7.5 and Node 8.9. Any idea of what could be wrong?

type : ps aux | grep node or ps aux | grep port(e.g 3000)

and find the process copy its processId then type in terminal kill -KILL processId

it will stop your process by force than again start server

nodemon stuck at restarting · Issue #1356 · remy/nodemon · GitHub, nodemon -v: 1.12.1 and 1.17.5 (I have tried nodemon@latest) node -v: 8.4.0 npm -v: 5.0.3 Operating system/terminal environment: Windows 10  Nodemon stuck at [nodemon] restarting due to changes #1544. Closed deveshsinghal22 opened this issue Mar 26, 2019 · 41 comments Closed

Try executing

npm -g uninstall nodemon

then

npm -g install nodemon

That fixed it for me.

Nodemon stuck at "restarting due to changes" and won't restart the , I am using window 10, and I faced this issue after I accidentally removed my %​PATH% variable. Try adding these three paths if it is the case:. Ed-Ed changed the title Nodemon stuck at restarting nodemon Stuck At Restarting May 30, 2018 Ed-Ed changed the title nodemon Stuck At Restarting nodemon stuck at restarting May 30, 2018 remy added the windows label May 31, 2018

I am using window 10, and I faced this issue after I accidentally removed my %PATH% variable. Try adding these three paths if it is the case:

C:\Windows; C:\Windows\system32; C:\Windows\System32\Wbem;

Developers - Nodemon stuck at restarting -, Nodemon detects file change, attempts to restart the server, but takes forever long to restart - stuck at restarting the server and the server never  Nodemon stuck at “restarting due to changes…” and won't restart the server. I have a pretty basic nodemon configuration. I'm fixing this legacy node 7 project that I inherited and trying to make the development process a little bit painful. First thing first, a proper restart-and-transpile process (since it's built using ES6 modules syntax).

Check whether you place your code in location without write permission. (Especially who put on Desktop) If no, please move the folder to other place with write permission. Or change the folder permission.

Nodemon stuck at [nodemon] restarting due to changes, nodemon -v : "^1.18.10"; node -v : v11.12.0; 'express -v':; Operating system/​terminal environment: WIN10; Using Docker? What image: no; Command you ran​:  I am using version 1.17.15 for about an hour now and it was stuck at restarting due to changes. The same issue in version 1.18.x. It stopped working after a trying to save changes multiple times before the "Starting node app.js" message appear.

Add the below path in the environment variable. It will solve your problem. %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\wbem;

Nodemon is stuck - Express / Node.js, nodemon is stuck while restarting the server again to see the changes i have to press ctrl+c and run again nodemon [nodemon] restarting due  Nodemon stuck at [nodemon] restarting due to changes hot 1 Nodemon crashes first restart then works ok the second one when started like nodemon --inspect=0.0.0.0:9229 app.js hot 1 Cannot clear console pre-start hot 1 contributors (According to the first 100)

Nodemon stuck at “restarting due to changes…” and won't restart the , Nodemon stuck at “restarting due to changes…” and won't restart the server - node.js. 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 is not restarting due to changes, I install nodemon <npm install -g nodemon>, I get the console message that all is going ok but when I change something in my app.js file the  Nodemon is a utility that will monitor for any changes in your source and automatically restart your server. It's perfect for development. The scenario is that, when you are working with Node.js server, every time any changes occur you should start the server again and again.

nodemon, nodemon reload, automatically. Nodemon is a utility that will monitor for any changes in your source and automatically restart your server. Perfect for  $ yarn add nodemon --dev # or, using npm: $ npm install nodemon --save-dev. As you can see, when doing a local install, we can install as a dev dependency. Note also that with a local install you won’t be able to use the nodemon command directly from the command line, but instead you can use it as part of some npm scripts, or with npx. Basic