stream: do not pass readable.compose() output via Readable.from()
#60907
+68
−40
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
readable.compose()was intended to return the Duplex constructed bystream.compose(), and is documented as such.However, because it was added as a "stream-returning operator", its output is being passed via
Readable.from(), which constructs a new object-mode Readable by consuming the async iterator of the composed Duplex. This is inefficient in the best case, but causes breakage in a load of others:stream.compose().This change gets rid of the "operator" semantics for
readable.compose(), and makes it a standalone method which returns the unaltered composed Duplex stream fromstream.compose().Fixes: #55203