-
-
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 doesn't kill the last listening port when resaving the project #2128
Comments
Hi @Bardala, Here are some methods you can try to solve your problem:-
If the issue persists, feel free to reach out for further assistance. I'm here to help. |
This happens to me too if I try to run two commands in sequence i.e. if I prefix |
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. |
The only reliable way I've found to handle graceful restarts with If your graceful exit code requires anything async though, you'll get random race conditions since nodemon isn't properly waiting for the process to exit before starting it again. See issue #1889 |
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. |
Automatically closing this issue due to lack of activity |
nodemon -v
: 3.0.1Expected behaviour
Actual behaviour
stackoverflow
The text was updated successfully, but these errors were encountered: