-
-
Notifications
You must be signed in to change notification settings - Fork 33.4k
Closed
Labels
docIssues and PRs related to the documentations.Issues and PRs related to the documentations.streamIssues and PRs related to the stream subsystem.Issues and PRs related to the stream subsystem.web streams

Description
Version
v16.7.0
Platform
No response
Subsystem
docs
What steps will reproduce the bug?
- https://nodejs.org/api/webstreams.html?expand=1#webstreams_class_compressionstream claims "v16.7.0"
- https://nodejs.org/api/webstreams.html?expand=1#webstreams_class_decompressionstream claims "v16.7.0"
This is incorrect, because they were added in 09ad64d which doesn't have a stable release yet (commit is only part of the master
branch).
So this isn't even part of v16.8.0 yet:
$ node
Welcome to Node.js v16.8.0.
Type ".help" for more information.
> const stream_web = require('stream/web');
undefined
> stream_web.TransformStream
[class TransformStream]
> stream_web.DecompressionStream
undefined
> stream_web.CompressionStream
undefined
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior?
Shouldn't appear in documentation, or at least be documented as unimplemented in stable versions.
Entries with added: REPLACEME
shouldn't be shown in docs (certainly not with a made-up version number).
I assume that "v16.7.0" for "REPLACEME" is used as an outdated placeholder as "next release version" somewhere.
This might also affect other classes like TextDecoderStream
and TextEncoderStream
which are available in stable releases, but still use "REPLACEME".
What do you see instead?
No response
Additional information
No response
Metadata
Metadata
Assignees
Labels
docIssues and PRs related to the documentations.Issues and PRs related to the documentations.streamIssues and PRs related to the stream subsystem.Issues and PRs related to the stream subsystem.web streams