Skip to content

Commit

Permalink
doc: clarify when child process 'spawn' event is *not* emitted
Browse files Browse the repository at this point in the history
Making this clarification in response to a comment on GitHub:
#35288 (comment)

PR-URL: #37833
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
  • Loading branch information
zenflow authored and targos committed May 1, 2021
1 parent 2551bb1 commit b31bb72
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions doc/api/child_process.md
Expand Up @@ -1088,6 +1088,8 @@ added: REPLACEME
-->

The `'spawn'` event is emitted once the child process has spawned successfully.
If the child process does not spawn successfully, the `'spawn'` event is not
emitted and the `'error'` event is emitted instead.

If emitted, the `'spawn'` event comes before all other events and before any
data is received via `stdout` or `stderr`.
Expand Down

0 comments on commit b31bb72

Please sign in to comment.