doc: clarify when child process 'spawn' event is *not* emitted · nodejs/node@b31bb72 · GitHub

nodejs / node Public

• Notifications You must be signed in to change notification settings
• Fork 36.6k
• Star 120k

• Code
• Issues 632
• Pull requests 754
• Actions
• Projects
• Security and quality
• Insights

Additional navigation options

Commit b31bb72

Browse filesBrowse the repository at this point in the historyBrowse files

zenflow

authored and

targos

committed

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
Copy full SHA for b31bb72

1 file changed

+2Lines changed: 2 additions & 0 deletions

File tree

Expand file treeCollapse file tree

Open diff view settings

Filter options

• doc/api
  • child_process.md

Expand file treeCollapse file tree

Open diff view settings

Collapse file

‎doc/api/child_process.md‎

Copy file name to clipboardExpand all lines: doc/api/child_process.md

+2Lines changed: 2 additions & 0 deletions

• Display the source diff
• Display the rich diff

Original file line number	Diff line number	Diff line change
@@ -1088,6 +1088,8 @@ added: REPLACEME
1088	1088	-->
1089	1089
1090	1090	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.
1091	1093
1092	1094	If emitted, the `'spawn'` event comes before all other events and before any
1093	1095	data is received via `stdout` or `stderr`.

0 commit comments

Comments

0 (0)