-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nodemon stuck at "[nodemon] restarting due to changes" #1915
Comments
I have the same problem, also 2.0.12. Running Windows. Have this problems since a few weeks. It's working about 5 times, then it stucks. |
I've solved the problem by not installing the latest nodemon version but the old one i.e. nodemon@2.0.7 |
I'm running into the same issue. Tried running 2.0.2 and 2.0.2(like mentioned in the other closed issue). Neither helped. Also running in verbose mode, I don't see anything suspicious. |
Try running nodemon version 2.0.7. It fixed my problem. |
I recently reinstalled my OS (windows 10). I started facing the same issue after that. I'm not sure which version of nodemon I was using before reinstalling my os. I tried different versions of nodemon to see if anything works. nodemon@2.0.7 works. nodemon@2.0.8 shows the following error pop up when I try to restart: nodemon@2.0.9 and nodemon@2.0.10 shows nothing and are stuck while restarting. I stopped testing after this. P.S: I use nodemon globally. |
this pr solves this issue : #1938 |
Can people following this thread test with |
I've had this issue for quite some time and I encounter this everyday, I'll be using this v of nodemon for the next 4 days and update what happens. |
Let's keep this open until the fix is actually live (for others with the same issue to prevent dupes). |
The issue is solved. Just use version 2.0.7 of nodemon. |
That solution drops additions for the fix; to me it makes more sense to make this a fix than to use an older version of nodemon. However, that may work for a temporary solution. |
Works 100%. Tested it about 50 times, restarted all the time (Windows) with 2.0.14 and 2.0.14-alpha.1 Tested also 2.0.12 again and also 2.0.13 and run into problems. @immortalmind2016 great, thanks for this fix! @remy 2.0.14 is live @ latest since a few minutes. You could close this issue. |
I didn't encountered any issues relating to this while using the alpha version last night, I even restarted nodemon extra times to make sure. LGTM! |
@mrmalik16 i am using windows 10, and it was working fine before, i don't what happened to it suddenly, tried changing environment variables and installing different versions but no luck so fat |
https://stackoverflow.com/questions/72758944/nodemon-does-not-auto-restart/72920135#72920135 I have found the solution if all the above recommendations doesn't work just like for me. |
@DevonChia i uninstalled node and install it again and it's working now, may be problem with node path in environment variables |
I have reinstalled many times but doesn't work, I guess the installation didnt manage to implement the variables correctly. Thus, I made the changes manually without the need to reinstall node |
this solution works for me: https://www.youtube.com/watch?v=a9fIZViTNEA&ab_channel=TechTalkNetwork |
I used powershell and it works fine, I'm guessing it may be an issue with cmd as on cmd it stays on "restarting due to changes" |
this solution also worked for me. after doing this ,just restart your computer if it doesnt work after restarting vscode |
Oh my god, I am gonna kill myself. After installing nodemon I was trying to run this
And it is actull should be
|
This solution works for me after restarting vscode |
nodemon -v
: 2.0.12node -v
: 14.17.6package.json
The text was updated successfully, but these errors were encountered: