-
-
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 restarting #1356
Comments
First question: does it suddenly drop into a restart loop? If so, can you include the output but run nodemon using the |
Hello, @remy I am somewhat active on GitHub, and have been facing the issue for quite a while now. Yes, sometimes it suddenly drops into a restart loop, and when I used Can't reproduce the bug now, using nodemon with EDIT: This is how it looks on the first start:
And this is how it looks when it keeps restarting (trimmed 700 lines in the middle)
|
as #1354 (comment) 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 : |
Hi all, it's been a long time but I found a solution to my problem at last. If I run nodemon locally, it works fine, it only does this when I run it globally. I've tried uninstalling and reinstalling globally, but no luck. No idea why this is the case, but we can close now. |
@TFKED how did you install nodemon locally? I used npm install nodemon without the g, but when I tried to run it, my terminal said that it doesn't recognize nodemon as a command. |
@AwesomeBanana123 it won't. You have to run it like this if running locally: |
nodemon -v
: 1.12.1 and 1.17.5 (I have tried nodemon@latest)node -v
: 8.4.0npm -v
: 5.0.3Expected 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.
The text was updated successfully, but these errors were encountered: