Exit process cleanly on SIGINT, SIGTERM, and SIGUSR2 signals #75
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
We are using this plugin for SSR workflow to take advantage of cssnext functionality. In our development workflow we run
babel-node
throughnodemon
. Whennodemon
restarts, it uses theSIGUSR2
signal to cause restarts in child processes. This plugin restarts and reports that it cannot create a new server because the existing one is already running and exists. (It seems to be because the socket didn't get cleaned up.) Also, when we exitnodemon
, we have to interrupt twice to get thepostcss-server
process to end.This PR represents the tweaks I came up with to use this plugin for our workflow. If it works for other work flows, it would be great if it could be merged!
The basic changes are to cause the
postcss-server
to exit on any of the handled signals and delegate theexit
handler to clean up the server socket (since it's called in all cases).Thanks!