Skip to content

mkOnClose reacts to the 'close' signal instead of 'exit' #17

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

Closed
wants to merge 1 commit into from

Conversation

Profpatsch
Copy link
Contributor

According to the node documentation:
'close' is distinct from the 'exit' event, since multiple processes might
share the same stdio streams.”

https://nodejs.org/api/child_process.html#child_process_event_close

Fixes #15

According to the node documentation:
“`'close'` is distinct from the 'exit' event, since multiple processes might
share the same stdio streams.”

https://nodejs.org/api/child_process.html#child_process_event_close
@kritzcreek kritzcreek mentioned this pull request May 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

(mk)onClose should fire on the "close" signal, not the "exit" signal
1 participant