-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fetch API to get ReadableStream #762
Comments
Sorry i don't know if this is the right place to post. Please help me in resolving the issue. |
This implementation of Fetch does not include readable stream support. Stack Overflow is the best place to ask usage questions. |
how come there are no plans to include readable stream support to this polyfill? is it too heavy? another idea @rakeshkota19 could be to add a polyfill on top of this polyfill :) I don't see why not.., like, whatwg-fetch-readablestream |
FYI, I've just tried https://www.npmjs.com/package/web-streams-polyfill in combination with whatwg-fetch and works well. for quick reference,
then fetch() with resp.body.getReader() will work |
|
I was trying to get reader of ReadableStream using getReader() and response.body of fetch. Even when i am not consuming data by calling read method, the buffer of stream is getting filled and it is even not applying any kind of backpressure and this is leading to huge memory usage. Is there any way to set WaterMark size on the ReadableStream returned by fetch. Is there any other way to control the buffer size of stream.
The text was updated successfully, but these errors were encountered: