Skip to content
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
fixup! doc: update spawnSync() status value possibilities
  • Loading branch information
Trott committed Mar 17, 2019
commit 28367bb966d81264ed6f799fc19eb17562a905db
5 changes: 3 additions & 2 deletions doc/api/child_process.md
Original file line number Diff line number Diff line change
Expand Up @@ -869,8 +869,9 @@ changes:
* `stdout` {Buffer|string} The contents of `output[1]`.
* `stderr` {Buffer|string} The contents of `output[2]`.
* `status` {number|null} The exit code of the subprocess, or `null` if the
child process exited due to a signal.
* `signal` {string} The signal used to kill the child process.
subprocess ended due to a signal.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't object to "ended", but please be aware that its non-standard terminology: streams end, processes terminate, on both posixy and windowsy operating systems, see:

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll switch to terminate since it's the best term for this.

* `signal` {string|null} The signal used to kill the subprocess, or `null` if
the subprocess did not end due to a signal.
* `error` {Error} The error object if the child process failed or timed out.

The `child_process.spawnSync()` method is generally identical to
Expand Down