Skip to content

Commit b31bb72

Browse files
zenflowtargos
authored andcommittedMay 1, 2021
doc: clarify when child process 'spawn' event is *not* emitted
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>
1 parent 2551bb1 commit b31bb72

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed
 

‎doc/api/child_process.md

+2
Original file line numberDiff line numberDiff line change
@@ -1088,6 +1088,8 @@ added: REPLACEME
10881088
-->
10891089

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

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

0 commit comments

Comments
 (0)
Please sign in to comment.