nodemon: 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: “nodemon ./bin/www”
Expected behaviour
express server should reload with
Listening on port 3300 MongoDB connection initiated....
Actual behaviour
$ npm start
> server@0.0.0 start --hidden-location
> nodemon ./bin/www
[nodemon] 1.18.10
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: *.*
[nodemon] starting `node ./bin/www`
Listening on port 3300
MongoDB connection initiated....
[nodemon] restarting due to changes...
[nodemon] restarting due to changes...
[nodemon] restarting due to changes...
[nodemon] restarting due to changes...
[nodemon] restarting due to changes...
[nodemon] restarting due to changes...
and stuck there
Steps to reproduce
I am just running npm start, which leads to “nodemon ./bin/www”
my package,json
{ "name": "server", "version": "0.0.0", "private": true, "scripts": { "start": "nodemon ./bin/www" }, "dependencies": { "amqplib": "^0.5.2", "async": "^2.6.1", "body-parser": "~1.18.2", "connect-mongo": "^2.0.1", "cookie-parser": "~1.4.3", "cors": "^2.8.4", "debug": "~2.6.9", "ejs": "~2.5.7", "express": "~4.15.5", "express-acl": "^2.0.4", "express-react-views": "^0.10.5", "express-session": "^1.15.6", "lodash": "^4.17.11", "mongoose": "^5.3.2", "morgan": "~1.9.0", "passport": "^0.4.0", "passport-google-oauth2": "^0.1.6", "react": "^16.5.2", "react-dom": "^16.5.2", "request": "^2.83.0", "serve-favicon": "~2.4.5", "socket.io": "^2.0.4" }, "devDependencies": { "nodemon": "^1.18.10" } }
Please let me know if you need any additional info.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 3
- Comments: 56 (4 by maintainers)
Commits related to this issue
- Add --signal SIGKILL This is required for some cases where nodemon gets stuck in a loop by detecting unexisting changes. See https://github.com/remy/nodemon/issues/1544#issuecomment-545756586 — committed to boostercloud/booster by NickSeagull 3 years ago
- Add --signal SIGKILL This is required for some cases where nodemon gets stuck in a loop by detecting unexisting changes. See https://github.com/remy/nodemon/issues/1544#issuecomment-545756586 — committed to boostercloud/booster by NickSeagull 3 years ago
- Add --signal SIGKILL This is required for some cases where nodemon gets stuck in a loop by detecting unexisting changes. See https://github.com/remy/nodemon/issues/1544#issuecomment-545756586 — committed to boostercloud/booster by NickSeagull 3 years ago
not stale.
Formatting and reinstalling windows worked for me
I still have this issue
not stale
Try adding
--signal SIGKILLto your nodemon command.@bjm904 sure, with details on how to replicate consistently.
issue is still there.
As crazy as it might sounds, I fixed it just restarting my computer (windows 10).
On Mon, May 13, 2019 at 11:41 PM Shu Pengfei notifications@github.com wrote:
To usando o node-dev que faz a mesma coisa O nodemon não consegui resolver
Resolvi meu problema com a dica da elzasimoes, muito obrigado Elza. Ela me recomendou utilizar o (node-dev) e funcionou.
I have this issue
Windows 10 node v12.16.1 npm 6.14.4 nodemon: 2.0.4
Guys, there is a simple very simple fix to that, please go to environment variables, select edit, and add a path for node js which can be "C:\Program Files\nodejs"
This solved my problem, this is for windows 10 not sure about oter os for similar issues
@remy Please re-open this issue
I still have this issue. I am using Windows 10. As a workaround, I too, am using forever. npx forever -w index.js
i have same problem on window 8.1 nodemon version = 1.19.0 node version = 10.15.1