Graduate WHATWG Streams from Experimental?

What else do we need to make sure gets done before graduating the WHATWG streams implementation from experimental?

/cc @nodejs/streams

I would add #39316 as well.

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.

I 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

@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..).

stream: remove whatwg streams experimental warning

stream: expose web streams globals, remove runtime experimental warning

Navigation Menu

Repository navigation

Graduate WHATWG Streams from Experimental? #40950

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Graduate WHATWG Streams from Experimental? #40950

Description

Activity

ronag commented on Nov 24, 2021

mcollina commented on Nov 24, 2021

benjamingr commented on Nov 25, 2021

ronag commented on Nov 25, 2021

benjamingr commented on Nov 25, 2021

mcollina commented on Nov 25, 2021

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions