-
Notifications
You must be signed in to change notification settings - Fork 30.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Full support of WhatWg Streams #36566
Comments
@nodejs/whatwg-stream |
Also the new WebSocketStream will be enable by default on Chrome 89 and deno has plan to implement it it based heavily on WHTWHG stream |
web streams have landed |
@ronag in which commit/PR? |
This was referenced Sep 13, 2022
This was referenced Sep 29, 2022
This was referenced Oct 5, 2022
This was referenced Oct 8, 2022
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
WhatWg Streams are part of having a browser compatible
fetch
implementation: (see: #19393). For better interoperability of browser and nodejs, it would be awesome to haveWhatWg
streams readily available in node, like we haveAbortController
,Event
andEventTarget
.There is a reference implementation of this available that uses the web-platform-tests test-suite to make sure it works as intended. Could that make a decent first version?
I am opening this issue as a follow up on #19393 (comment) and as a means to watch an issue to see if there is some progress or consensus on that topic. I don't think I have much time to spend on this.
The text was updated successfully, but these errors were encountered: