Commit e48cc3c
doc: remove confusing note about child process stdio
It’s not obvious what the paragraph is supposed to say.
In particular, whether and what kind of buffering mechanism
a process uses for its stdio streams does not affect that,
in general, no guarantees can be made about when it consumes data
that was sent to it.
PR-URL: #19552
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>1 parent 9d249bf commit e48cc3c
1 file changed
Lines changed: 0 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -32,10 +32,6 @@ stdout in excess of that limit without the output being captured, the child | |||
| 32 | 32 | process will block waiting for the pipe buffer to accept more data. This is | |
| 33 | 33 | identical to the behavior of pipes in the shell. Use the `{ stdio: 'ignore' }` | |
| 34 | 34 | option if the output will not be consumed. | |
| 35 | - It is possible to stream data through these pipes in a non-blocking way. Note, | ||
| 36 | - however, that some programs use line-buffered I/O internally. While that does | ||
| 37 | - not affect Node.js, it can mean that data sent to the child process may not be | ||
| 38 | - immediately consumed. | ||
| 39 | 35 | ||
| 40 | 36 | The [`child_process.spawn()`][] method spawns the child process asynchronously, | |
| 41 | 37 | without blocking the Node.js event loop. The [`child_process.spawnSync()`][] | |
0 commit comments