Rule proposal: Prefer `stream.pipeline` over `stream.Readable#pipe` in Node.js

Repository metrics

Stars

5,022 stars (5,022 stars)

PR merge metrics

Avg merge 1d 16h (Avg merge 1d 16h)399 merged PRs in 30d (399 merged PRs in 30d)

Description

Contributor guide

Research direction

The proposal requires implementing a new ESLint rule. First, understand how to obtain type information via the typescript eslint project (see issue #542). Then, design the rule logic to detect usage of stream.Readable#pipe and suggest using stream.pipeline. Look at existing rules in the eslint plugin unicorn rules directory for style guidance. No linked PRs or assignees.

Tech stack

javascriptnodejs

Domain

developer experiencetooling

Issue type

Feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

Half day

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

Stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Needs investigation

Prerequisites

Node.js streamsESLint custom rulesTypeScript (optional)

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

30