Repository navigation
Graduate WHATWG Streams from Experimental? #40950
Description
Activity
I don't think they've seen enough usage and adoption and I'd like us to be able to change them before we do.
I don't think there is rush to graduate them yet (is there?), I suspect once the community uses them more we'll uncover issues that might require breaking changes (in errors or API guarantees) and I believe that graduating them doesn't get us much and costs us the ability to make changes without long deprecation cycles.
Reacted by Vitali KuzmichI suspect once the community uses them more we'll uncover issues that might require breaking changes
How do we make this happen? i.e. more people uses them.
@ronag I think we just wait and also ship other experimental APIs that use them?
We can also reach out to the community and explicitly ask for feedback
I think we could just drop the console warning on them and keep them as experimental in the docs (the same is true for Blob, File, etc..).
Reacted by Robert Nagy and Benjamin Gruenbaum- added a commit that references this issue
on Dec 1, 2021 - added a commit that references this issue
on Jan 31, 2022 - added a commit that references this issue
on Feb 1, 2022 - added a commit that references this issue
on Apr 4, 2022 - added a commit that references this issue
on Apr 25, 2022
What else do we need to make sure gets done before graduating the WHATWG streams implementation from experimental?
/cc @nodejs/streams