delayed-stream
npmv1.0.0Buffers events from a stream until you are ready to handle them.
Not recommended for new projects
No — delayed-stream should not be adopted for new projects. Last published 4150 days ago.
- AAdoption: grade A, Excellent.
106.4M downloads per week and 1 known dependents.
- FMaintenance: grade F, Failing.
Last published 4150 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies.
- ASupply chain: grade A, Excellent.
No install scripts, 2 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 delayed-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.
Compatibility
- Node.js
- node >=0.4.0
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the delayed-stream README.
var DelayedStream = require('delayed-stream');
var http = require('http');
http.createServer(function(req, res) {
var delayed = DelayedStream.create(req);
setTimeout(function() {
res.writeHead(200);
delayed.pipe(res);
}, 1000);
});Dependencies
Declared by delayed-stream v1.0.0. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (2)
Used by
Popular packages that depend on delayed-stream.
Relationship graph
Dependencies (left) and dependents (right) of delayed-stream.
Release history
No releases in the last two years, typically about 0 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 1.0.0latest | 11 years ago | — | MIT |
| 0.0.7 | 11 years ago | — | MIT |
| 0.0.6 | 11 years ago | — | MIT |
| 0.0.5 | 15 years ago | — | MIT |
| 0.0.4 | 15 years ago | — | MIT |
| 0.0.3 | 15 years ago | — | MIT |
| 0.0.2 | 15 years ago | — | MIT |
| 0.0.1 | 15 years ago | — | MIT |
| 0.0.0 | 15 years ago | — | MIT |
Overview
delayed-stream is an npm package that buffers events from a stream until you are ready to handle them. It is extremely widely used, with about 106.4M downloads per week and 1 known dependents in the graph. The latest version is 1.0.0, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need buffers events from a stream until you are ready to handle them and value a battle-tested, widely-adopted 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
- Large, well-established user base (106.4M weekly downloads).
- 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.
Frequently asked questions
Should I use delayed-stream?
No — delayed-stream should not be adopted for new projects. Last published 4150 days ago.
How do I install delayed-stream?
Run `npm install delayed-stream` to add delayed-stream to your npm project.
What license is delayed-stream released under?
delayed-stream is distributed under the MIT license.
How popular is delayed-stream?
delayed-stream has approximately 106,389,061 downloads per week and 1 known dependent packages.
Is delayed-stream still maintained?
The most recent release of delayed-stream (v1.0.0) was published 11 years ago.
Does delayed-stream run install scripts?
No. delayed-stream does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.