Commit 261672b
doc: remove obsolete stream API selection text
PR-URL: #42586
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Robert Nagy <ronagy@icloud.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Akhil Marsonya <akhil.marsonya27@gmail.com>1 parent 1f7d2e8 commit 261672b
1 file changed
Lines changed: 0 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -863,11 +863,6 @@ to consume data from a single stream. Specifically, using a combination | |||
| 863 | 863 | of `on('data')`, `on('readable')`, `pipe()`, or async iterators could | |
| 864 | 864 | lead to unintuitive behavior. | |
| 865 | 865 | ||
| 866 | - `readable.pipe()` provides the easiest way to consume stream data. Developers | ||
| 867 | - that require more fine-grained control over the transfer and generation of data | ||
| 868 | - can use the [`EventEmitter`][] and `readable.on('readable')`/`readable.read()` | ||
| 869 | - or the `readable.pause()`/`readable.resume()` APIs. | ||
| 870 | - | ||
| 871 | 866 | #### Class: `stream.Readable` | |
| 872 | 867 | ||
| 873 | 868 | <!-- YAML | |
0 commit comments