nodemon: nodemon 1.18.9 not working in windows 10 *64

I have installed nodemon npm install nodemon --g and the server is starting as it is suppose to but then while i change in my file it says restarting due to changes… and nothing other then this line and the weird thing is the server didnot restart i have restarted my pc tried updating the nodemon my friend is using same thing and in his computer it worked but not mine. I m not sure what the isuue is. Can anyone help me here. nodemon index.js [nodemon] 1.18.9 [nodemon] to restart at any time, enterrs[nodemon] watching: *.* [nodemon] startingnode index.js the app is running.... [nodemon] restarting due to changes...

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 48 (6 by maintainers)

Most upvoted comments

@remy sorry for the delay - I’ve just set up a simple package with nothing but nodemon and the basic “hello world” app.js file. I’m using nodemon as a dev dependency, and my yarn start is set to nodemon app.js. When I start it, I get the usual message:

 ⨯ Lemuel Cushing@CUTHBERT  C\..\nodemon_test  yarn start
yarn run v1.13.0
$ nodemon app.js
[nodemon] 1.18.10
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: *.*
[nodemon] starting `node app.js`
Server running at http://127.0.0.1:3000/

When I make a change to app.js and save it, I get [nodemon] restarting due to changes... Which just hangs.

If I add the -V flag, the follwing is displayed:

 Lemuel Cushing@CUTHBERT  C\..\nodemon_test  yarn start
yarn run v1.13.0
$ nodemon -V app.js
[nodemon] 1.18.10
[nodemon] to restart at any time, enter `rs`
[nodemon] or send SIGHUP to 34116 to restart
[nodemon] watching: *.*
[nodemon] watching extensions: js,mjs,json
[nodemon] starting `node app.js`
[nodemon] forking
[nodemon] child pid: 10640
[nodemon] watching 3 files
Server running at http://127.0.0.1:3000/

And after I save a change:

[nodemon] files triggering change check: app.js
[nodemon] matched rule: **\*.*
[nodemon] changes after filters (before/after): 1/1
[nodemon] restarting due to changes...
[nodemon] app.js

[nodemon] files triggering change check: app.js
[nodemon] matched rule: **\*.*
[nodemon] changes after filters (before/after): 1/1
[nodemon] restarting due to changes...
[nodemon] app.js

Care to debug rather than “me too”? Happy to take PRs that will fix or even some actual debugging information to replicate and fix…

  1. Start Windows PowerShell with the “Run as Administrator” option. Only members of the Administrators group on the computer can change the execution policy.

  2. Enable running unsigned scripts by entering:

    set-executionpolicy remotesigned

You should run PowerShell as administrator then: PS C:\WINDOWS\system32> Set-ExecutionPolicy RemoteSigned and press A

I had the same problem on win 7. The issue was founded accidentally. My solution was adding C:\Windows\System32\ to the system variable in the PATH.

I got this glitch after installing the latest update of nodemon. So I tried to revert back to the old version and it doesn’t do anything. I think the update does something on the windows operating system that cannot remove even after uninstall and installing (reinstall) the nodemon package. I believe the problem can be solve by reinstalling the os as stated on the previous Issue, https://github.com/remy/nodemon/issues/1461#issuecomment-442487389 but this isn’t an efficient fix.

This issue has been automatically marked as idle and stale because it hasn’t had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up. Thank you for contributing ❤️