-
Notifications
You must be signed in to change notification settings - Fork 4
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
Stream body support? #25
Comments
Hey, might be too late for your use case by now but I'll have a look and see if I can add stream support. |
* feat: add support for response streams * ci: enable AbortController on Node 14 * feat: support streaming request body fix #25
🎉 This issue has been resolved in version 5.1.0-next.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Awesome, thanks! :) |
Ha, wasn't sure if you were still interested in this after ... 7-8 months. I've published it under the |
* feat: add support for response streams (#134) * feat: add support for response streams * ci: enable AbortController on Node 14 * feat: support streaming request body fix #25 * chore(release): 5.1.0-next.1 [skip ci] # [5.1.0-next.1](v5.0.2...v5.1.0-next.1) (2022-04-10) ### Features * add support for response streams ([#134](#134)) ([abc1732](abc1732)), closes [#25](#25) Co-authored-by: semantic-release-bot <[email protected]>
This is an empty commit in order to get semantic-release to publish the code that was merged through a squash-and-merge action. fix #25
# [5.1.0](v5.0.2...v5.1.0) (2022-04-19) ### Features * support streams ([4ef2b66](4ef2b66)), closes [#25](#25)
🎉 This issue has been resolved in version 5.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Hi, I'm scoping out your library :)
When looking at response.ts it seems that if the body is a stream, that's not supported, right? I'm new to
got
so not sure how streams work.If that's the case, would that be solved by using the
consumeBody
function fromnode-fetch
?The text was updated successfully, but these errors were encountered: