</>PackageGraphPackageGraph

merge-stream

npmv2.0.0

Create a stream that emits events from multiple other streams

Not recommended for new projects

No — merge-stream should not be adopted for new projects. Last published 2666 days ago.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • FMaintenance: grade F, Failing.

    Last published 2666 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 4.2 KB installed.

  • ASupply chain: grade A, Excellent.

    No install scripts, 3 maintainers, and a contained dependency surface.

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding merge-stream to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

4.2 KB
Install size

Unpacked size of this package plus its entire runtime tree.

—
Tree depth

Longest resolved dependency chain below this package.

Compatibility

Node.js
No constraint declared
Module format
CommonJS only
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the merge-stream README.

javascriptFull README ↗
var stream1 = new Stream();
var stream2 = new Stream();

var merged = mergeStream(stream1, stream2);

var stream3 = new Stream();
merged.add(stream3);
merged.isEmpty();
//=> false

Dependencies

Declared by merge-stream v2.0.0. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (2)

from2 ^2.0.3istanbul ^0.4.5

Used by

Popular packages that depend on merge-stream.

jest-workernpm

Module for executing heavy tasks under forked processes in parallel, by providing a `Promise` based interface, minimum overhead, and bound workers.

↓ 0/wk◈ 8 dependents⚖ MITTS
fbjsnpm

A collection of utility libraries used by other Facebook JS projects

↓ 0/wk◈ 1 dependents⚖ MIT

Relationship graph

Dependencies (left) and dependents (right) of merge-stream.

jest-workerfbjsmerge-stream
merge-stream dependencies dependents

Frequently installed together

jest-utilnpm

This packages is a collection of utilities and helper functions

↓ 104M/wk◈ 23 dependents⚖ MITTS
@ungap/structured-clonenpm

A structuredClone polyfill

↓ 75.6M/wk◈ 2 dependents⚖ ISC
@types/nodenpm

TypeScript definitions for node

↓ 0/wk◈ 327 dependents⚖ MITTS
jest-leak-detectornpm

Module for verifying whether an object has been garbage collected or not.

↓ 0/wk◈ 2 dependents⚖ MITTS
loose-envifynpm

Fast (and loose) selective `process.env` replacer using js-tokens instead of an AST

↓ 65M/wk◈ 2 dependents⚖ MIT
setimmediatenpm

A shim for the setImmediate efficient script yielding API

↓ 50.7M/wk◈ 2 dependents⚖ MIT
cross-fetchnpm

Universal WHATWG Fetch API for Node, Browsers and React Native

↓ 32.9M/wk◈ 2 dependents⚖ MITTS
fbjs-css-varsnpm

This package exports a few of the CSS variables that we use in Facebook projects. This is not the full list we have internally but focused on making available the minimum set needed by our open source projects.

↓ 8.4M/wk◈ 1 dependents⚖ MIT
promisenpm

Bare bones Promises/A+ implementation

↓ 0/wk◈ 5 dependents⚖ MIT
immutablenpm

Immutable Data Collections

↓ 0/wk◈ 7 dependents⚖ MITTS
ua-parser-jsnpm

Detect Browser, Engine, OS, CPU, and Device type/model from User-Agent & Client Hints data. Supports browser & node.js environment

↓ 0/wk◈ 1 dependents⚖ AGPL-3.0-or-laterTS
jest-clinpm

Delightful JavaScript Testing.

↓ 0/wk◈ 3 dependents⚖ MITTS

Release history

No releases in the last two years, typically about 80 days apart.

Recent versions of merge-stream
VersionPublishedSizeLicense
2.0.0latest7 years ago4.2 KBMIT
1.0.19 years ago—MIT
1.0.011 years ago—MIT
0.1.811 years ago—MIT
0.1.711 years ago—MIT
0.1.612 years ago—MIT
0.1.512 years ago—MIT
0.1.412 years ago—MIT
0.1.312 years ago—MIT
0.1.212 years ago—MIT
0.1.112 years ago—MIT
0.0.112 years ago—MIT
0.0.013 years ago—MIT

Overview

merge-stream is an npm package that create a stream that emits events from multiple other streams. It has 2 known dependents in the graph. The latest version is 2.0.0, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need create a stream that emits events from multiple other streams and value a focused solution.

When not to use it

Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

  • Clear open-source license (MIT).
  • Lean dependency tree (2 direct dependencies).

Cons

  • No bundled TypeScript types (may require a separate @types package).

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

grncdrshinnnstevemao

Frequently asked questions

Should I use merge-stream?

No — merge-stream should not be adopted for new projects. Last published 2666 days ago.

How do I install merge-stream?

Run `npm install merge-stream` to add merge-stream to your npm project.

What license is merge-stream released under?

merge-stream is distributed under the MIT license.

How popular is merge-stream?

npm does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on merge-stream.

Is merge-stream still maintained?

The most recent release of merge-stream (v2.0.0) was published 7 years ago.

Does merge-stream run install scripts?

No. merge-stream does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.