merge2 is a Node.js utility for merging multiple streams into a single output stream, either in sequence or in parallel. It is useful for chaining stream pipelines (for example, bundling or processing multiple inputs) while controlling merge order and signaling completion via events like queueDrain.
Project status
- The project appears to be quiet or in maintenance mode for published npm updates, with the last clearly documented package updates dated 2020-06-03 (v1.4.0, v1.4.1), and no evidence provided of subsequent published updates up to today (2026-06-09). The GitHub upstream shows a push on 2026-01-21, but there are no accompanying details here about user-facing updates.
- Update cadence is very sparse and irregular: multiple updates occurred in 2017 to 2018, then fewer in 2019 and another burst in mid-2020, followed by a multi-year gap in the provided package update history.
AI summary generated
Recent updates
v1.4.1
Release v1.4.1 updates the merge2 stream implementation with mostly internal refactoring. There were no release notes provided by the publisher, so the actual behavior changes must be inferred from the code diff.
v1.4.0
v1.4.0 updates the merge2 library by adding an opt-in option to forward errors from piped source streams to the merged output stream. It also raises the supported Node.js engine version and bumps several dev dependencies (reflected heavily in package-lock.json). Release notes were not provided, so these changes are not documented by the publisher.
BreakingFeaturesv1.3.0
Release v1.3.0 was published on 2019-09-13, but no release notes or changelog details were provided by the publisher. As a result, there is no information available to determine whether this upgrade includes new features, bug fixes, breaking changes, or security updates.
v1.2.4
This release updates the package version to v1.2.4 and refreshes development tooling. The release notes section is empty, so the changes shown in the repository (CI config, version bump, devDependency upgrades, and the resulting lockfile churn) are effectively undocumented.
v1.2.3
Release v1.2.3 includes a small set of code changes centered around formatting and ESM export structure, plus updates to tests and development tooling. No release notes were provided, so the changes below are inferred strictly from the code diff.
Featuresv1.2.2
No release notes were provided for v1.2.2. The actual changes are limited to CI configuration and dev tool dependency version bumps.
v1.2.1
Release v1.2.1 updates the library version and makes small but behaviorally significant changes inside the core merge2 implementation. Release notes were not provided, so the code diff is the only source of truth for what changed.
Featuresv1.2.0
Release v1.2.0 contains no release notes. The code diff shows the addition of a new ESM entry point (index.mjs) and several package/test/CI metadata updates, with no corresponding documentation provided.
Featuresv1.1.0
The v1.1.0 release has no publisher-provided release notes, so all changes must be inferred from the code and repo diffs. The main functional code changes are minimal, mostly refactoring to modern JavaScript syntax, while the most significant change is a raised minimum Node.js version in package metadata and CI.
Breakingv1.0.3
Release v1.0.3 was published, but no release notes or change log details were provided by the publisher. As a result, no specific new features, breaking changes, fixes, or other developer-impacting modifications can be confidently identified from the provided material.