pump is a small Node module that pipes multiple streams together and ensures they are all destroyed if one of them closes or errors. It helps when standard `source.pipe(dest)` does not destroy the source on destination close and when you want a callback when the piping finishes.
Project status
- Maintenance: Looks actively maintained, with a recent update on 2026-02-28 (v3.0.4), about 5.5 months before today (2026-08-12).
- Update cadence: Updates appear irregular but relatively steady, with the last three updates dated 2024-09-11, 2025-06-16, and 2026-02-28 (roughly 8 to 9 months between each of the last two).
AI summary generated
Recent updates
v3.0.4
Release v3.0.4 contains only a small set of packaging changes plus a version bump. The code diff shows no changes to stream piping logic itself, but it introduces a new internal fs stub mechanism via package.json import mappings.
Breakingv3.0.3
Release v3.0.3 has no release notes provided by the publisher. The code diff shows a small compatibility-related change in index.js, plus version bumps in package.json and package-lock.json.
v3.0.2
Release v3.0.2 was published on 2024-09-11, but no release notes were provided by the publisher. As a result, this release cannot be reviewed for documented changes, potential breaking changes, or required migrations based on release-note content alone.
v3.0.1
v3.0.1 primarily makes a small change to how `pump` loads its `fs` dependency, preventing immediate failures in environments where `fs` is unavailable. The release notes do not provide any changelog content, but the repo includes notable documentation, security contact, and packaging metadata updates (README, funding, lockfile).
Securityv3.0.0
Release v3.0.0 makes a behavioral change to the main exported function, `pump()`, by adding an explicit return value. The README was updated to describe the new behavior, and tests were added to verify that `pump()` returns the last stream passed in.
v2.0.1
v2.0.1 makes a small internal change in stream type detection in index.js, and updates the test setup and test files. No release notes were provided, so all behavioral implications come from the code diff.
v2.0.0
Release v2.0.0 shows a small code change across 3 files, with the most notable change being in index.js. The project version was bumped, and the test suite was updated to assert the new return behavior.
v1.0.3
Release v1.0.3 contains a very small code change in the stream destruction logic for filesystem streams. Release notes were not provided, so the change is not described externally.
v1.0.2
Release v1.0.2 has no publisher-provided release notes. The code changes focus on improving browser compatibility by guarding access to Node's fs module and adding a browser-focused test.
Featuresv1.0.1
Release v1.0.1 was published on 2015-10-23, but no release notes or change log details were provided by the publisher. As a result, there is no documented information about new features, breaking changes, bug fixes, security updates, or dependency changes.