[Fizz/Flight] pipeToNodeWritable(..., writable).startWriting() -> renderToPipeableStream(...).pipe(writable) (#22450)

* Rename pipeToNodeWritable to renderToNodePipe

* Add startWriting API to Flight

We don't really need it in this case because there's way less reason to
delay the stream in Flight.

* Pass the destination to startWriting instead of renderToNode

* Rename startWriting to pipe

This mirrors the ReadableStream API in Node

* Error codes

* Rename to renderToPipeableStream

This mimics the renderToReadableStream API for the browser.
This commit is contained in:
Sebastian Markbåge
2021-10-06 00:31:06 -04:00
committed by GitHub
parent bc84c79555
commit 9f41b5fa3e
11 changed files with 169 additions and 178 deletions
+2 -1
View File
@@ -401,5 +401,6 @@
"413": "Expected finished root and lanes to be set. This is a bug in React.",
"414": "Did not expect this call in production. This is a bug in React. Please file an issue.",
"415": "Error parsing the data. It's probably an error code or network corruption.",
"416": "This environment don't support binary chunks."
"416": "This environment don't support binary chunks.",
"417": "React currently only supports piping to one writable stream."
}