Skip to content

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

Closed
Profpatsch wants to merge 1 commit into
purescript-node:masterfrom
Profpatsch:close-not-exit
Closed

mkOnClose reacts to the 'close' signal instead of 'exit'#17
Profpatsch wants to merge 1 commit into
purescript-node:masterfrom
Profpatsch:close-not-exit

Conversation

@Profpatsch
Copy link
Copy Markdown
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