-
Notifications
You must be signed in to change notification settings - Fork 64
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
Unable to abort process after server restart #36
Comments
Good find! I'll check it out! |
I appreciate it! |
DaftMonk
added a commit
to DaftMonk/grunt-express-server
that referenced
this issue
Jan 31, 2014
Was removing listener for ending process through ctrl+c. Now only removes listeners added by the start method. fixes ericclemmons#36
I'm sure you're very busy so I thought I'd add a PR for this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a watch task that restarts the server whenever a file is changed. When the server first starts I can use the abort command
ctrl+c
in the command prompt to stop the server.However, if I trigger the watch task to restart the server, I am no longer able to abort the process. Discovered this issue while investigating angular-fullstack/generator-angular-fullstack#52
After experimenting with the code I found that I could fix this by editing the stop method in the grunt-express-server and removing this line:
I think that it must be removing the listener for the abort command.
The text was updated successfully, but these errors were encountered: