feat: add prefer-stream-pipeline rule - #539
Draft
aladdin-add with Copilot wants to merge 4 commits into
Draft
Conversation
Copilot
AI
changed the title
[WIP] Add rule to prefer stream.pipeline over stream.Readable#pipe
feat: add Jun 19, 2026
prefer-stream-pipeline rule
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The standard
Stream#pipe()method requires manual error handling for each stream in the pipeline, which is verbose and error-prone. Node.js providesstream.pipeline()to handle error forwarding and stream cleanup automatically across the entire stream chain.Changes
prefer-stream-pipeline): Flags usages of.pipe()inCallExpressionnodes, prompting developers to usepipelinefromstreamorstream/promisesinstead.all-rules.jsindex, generated the corresponding Markdown documentation, and updated the README rule list.Example