"Bring your own stream"

(Just a question for me to consider in future.)

Is it possible to allow users to bring their own stream implementation, thus satisfy demands from both node stream and web stream camps? We did exactly that during the node <1 era when Promise isn’t native yet. Perhaps it’s time for that again…

[jimmywarting]

NodeJS community have wanted to get fetch into core https://github.com/nodejs/node/issues/19393

…They listen and they are going for it. To ship it they need to implement many underlying methods such as Blob, AbortSignal, and many more like the whatwg stream that is part of fetch’s response.body first

So they added whatwg streams in node v16.5 as experimental: https://github.com/nodejs/node/pull/39062

we could shim it using a polyfill.

For ppl that still want/need a node:stream with .pipe() can do: stream.Readable.from(iterable_or_responseBody) or use the for await (let chunk of res.body).

Think we are still going to support uploading node:streams with Requests but the Body.body are going to return a speced whatwg:stream instead

[jimmywarting]

if https://github.com/whatwg/streams/issues/1018 gets implemented in both node and whatwg stream then maybe we can just keep the current stream that we are using.

Then they could use their own stream as they like.

res = await fetch(url)
ReadableStream.from(res.body)