Skip to content

Commit c0a424f

Browse files
zenflowruyadorno
authored andcommitted
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 <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: James M Snell <[email protected]>
1 parent 9557dda commit c0a424f

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
@@ -1162,6 +1162,8 @@ added: v15.1.0
11621162
-->
11631163

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

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

0 commit comments

Comments
 (0)