combined-stream
npmv1.0.8A stream that emits multiple other streams one after another.
Not recommended for new projects
No — combined-stream should not be adopted for new projects. Last published 2677 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 2677 days ago.
- AWeight: grade A, Excellent.
Pulls in 1 transitive package, about 11 KB installed.
- ASupply chain: grade A, Excellent.
No install scripts, 4 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 combined-stream to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Licenses in the dependency tree
Every license you inherit by installing combined-stream, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node >= 0.8
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the combined-stream README.
var CombinedStream = require('combined-stream');
var fs = require('fs');
var combinedStream = CombinedStream.create();
combinedStream.append(fs.createReadStream('file1.txt'));
combinedStream.append(fs.createReadStream('file2.txt'));
combinedStream.pipe(fs.createWriteStream('combined.txt'));Dependencies
Declared by combined-stream v1.0.8. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (1)
Dev (1)
Used by
Popular packages that depend on combined-stream.
Relationship graph
Dependencies (left) and dependents (right) of combined-stream.
Frequently installed together
The ultimate javascript content-type utility.
RFC9562 UUIDs
An AST-based pattern checker for JavaScript.
Port of jQuery.extend for node.js and the browser
HTTP proxy tunneling agent. Formerly part of mikeal/request, now a standalone module.
Like JSON.stringify, but doesn't blow up on circular refs.
Signs and prepares requests using AWS Signature Version 4
Reference implementation of Joyent's HTTP Signature scheme.
Caseless object set/get/has, very useful when working with HTTP headers.
AWS signing. Originally pulled from LearnBoost/knox, maintained as vendor in request, now a standalone module.
OAuth 1 signing. Formerly a vendor lib in mikeal/request, now a standalone module.
Simplified HTTP request client.
Release history
No releases in the last two years, typically about 26 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 1.0.8latest | 7 years ago | 11 KB | MIT |
| 1.0.7 | 8 years ago | 11 KB | MIT |
| 1.0.6 | 8 years ago | 11 KB | MIT |
| 1.0.6-rc1 | 8 years ago | 11 KB | MIT |
| 1.0.5 | 11 years ago | — | MIT |
| 1.0.4 | 11 years ago | — | MIT |
| 1.0.3 | 11 years ago | — | MIT |
| 1.0.2 | 11 years ago | — | MIT |
| 1.0.1 | 11 years ago | — | MIT |
| 1.0.0 | 11 years ago | — | MIT |
| 0.0.7 | 12 years ago | — | MIT |
| 0.0.5 | 12 years ago | — | MIT |
| 0.0.4 | 13 years ago | — | MIT |
| 0.0.3 | 15 years ago | — | MIT |
| 0.0.2 | 15 years ago | — | MIT |
Overview
combined-stream is an npm package that a stream that emits multiple other streams one after another. It has 2 known dependents in the graph. The latest version is 1.0.8, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need a stream that emits multiple other streams one after another 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
Frequently asked questions
Should I use combined-stream?
No — combined-stream should not be adopted for new projects. Last published 2677 days ago.
How do I install combined-stream?
Run `npm install combined-stream` to add combined-stream to your npm project.
How many dependencies does combined-stream have?
combined-stream declares 2 direct dependencies and pulls in 1 packages in total once its runtime tree is resolved totalling about 11 KB on disk.
What license is combined-stream released under?
combined-stream is distributed under the MIT license.
How popular is combined-stream?
npm does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on combined-stream.
Is combined-stream still maintained?
The most recent release of combined-stream (v1.0.8) was published 7 years ago.
Does combined-stream run install scripts?
No. combined-stream does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.