nodemon stuck at restarting
See original GitHub issuenodemon -v: 1.12.1 and 1.17.5 (I have tried nodemon@latest)node -v: 8.4.0npm -v: 5.0.3- Operating system/terminal environment: Windows 10 using Node.js command prompt
- Command you ran: nodemon
Expected behaviour
When I save my sever.js file, it should console.log(‘test’) again and the port it is listening at.
Actual behaviour
Steps to reproduce
Not sure how to reproduce it.
It is the exact same issue as: #813
I know this isn’t a lot of information, but I don’t know much and I’m hoping by creating this it will highlight if I’m not the only one with this issue. If you need anything else from me, please let me know.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Nodemon stuck at "[nodemon] restarting due to changes"
Try running nodemon version 2.0.7. It fixed my problem.
Read more >Nodemon stuck at "restarting due to changes..." and won't ...
I am using window 10, and I faced this issue after I accidentally removed my %PATH% variable. Try adding these three paths if...
Read more >Npm start does not start app - nodemon just hangs
Hello! I'm just getting going, and I've installed the packages with 'npm install' and updated my .env file. However, when I try to...
Read more >Automatically Restart Node Apps on File Change with ...
In this short tutorial, learn how to restart Node/JavaScript applications automatically when you change a source file with Nodemon.
Read more >nodemon waiting for changes before restart
1. Go to the task manager 2. Then look for Node.js: Server-side JavaScript 3. Then right click on it and End task from...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
as https://github.com/remy/nodemon/issues/1354#issuecomment-392681579 try to run
fsutil behavior set disablelastaccess 1from an elevated shell.did it fix it?
Gave it a try, as an initial result, the bug was fixed.
I’ll post here if the issue happens again.
EDIT : 3 days after, the bug hasn’t still come back. https://github.com/remy/nodemon/issues/1354#issuecomment-392681579 probably solves it!