Gathering detailed insights and metrics for lazystream
Gathering detailed insights and metrics for lazystream
Gathering detailed insights and metrics for lazystream
Gathering detailed insights and metrics for lazystream
@types/lazystream
TypeScript definitions for lazystream
async-lazystream
Open Node Streams on demand with async support (original code from https://github.com/jpommerening/node-lazystream)
lazystream.ts
LazyStream.TS provides an easy way to work with collections in FP-like and SQL-like styles.
@rpai/lazystream
Open Node Streams on demand.
Create streams lazily when they are accessed (read from/written to).
npm install lazystream
Typescript
Module System
Min. Node Version
Node Version
NPM Version
99.2
Supply Chain
100
Quality
74.5
Maintenance
100
Vulnerability
100
License
JavaScript (100%)
Total Downloads
2,018,337,899
Last Day
555,479
Last Week
10,775,106
Last Month
46,292,980
Last Year
488,731,602
MIT License
55 Stars
25 Commits
11 Forks
2 Watchers
1 Branches
2 Contributors
Updated on May 05, 2025
Minified
Minified + Gzipped
Latest Version
1.0.1
Package Id
lazystream@1.0.1
Size
4.74 kB
NPM Version
6.14.15
Node Version
12.22.7
Published on
Oct 23, 2021
Cumulative downloads
Total Downloads
Last Day
6.9%
555,479
Compared to previous day
Last Week
-6.2%
10,775,106
Compared to previous week
Last Month
1.9%
46,292,980
Compared to previous month
Last Year
21.5%
488,731,602
Compared to previous year
1
1
Create streams lazily when they are read from or written to.
lazystream: 1.0.1
Sometimes you feel the itch to open all the files at once. You want to pass a bunch of streams around, so the consumer does not need to worry where the data comes from.
From a software design point-of-view this sounds entirely reasonable. Then there is that neat little function fs.createReadStream()
that opens a file and gives you a nice fs.ReadStream
to pass around, so you use what the mighty creator deities of node bestowed upon you.
Error: EMFILE, too many open files
─ node
This package provides two classes based on the node's Streams3 API (courtesy of readable-stream
to ensure a stable version).
A wrapper for readable streams. Extends stream.PassThrough
.
fn
{Function}options
{Object}PassThrough
stream, accessible by fn
.Creates a new readable stream. Once the stream is accessed (for example when you call its read()
method, or attach a data
-event listener) the fn
function is called with the outer lazystream.Readable
instance bound to this
.
If you pass an options
object to the constuctor, you can access it in your fn
function.
1new lazystream.Readable(function (options) { 2 return fs.createReadStream('/dev/urandom'); 3});
A wrapper for writable streams. Extends stream.PassThrough
.
fn
{Function}options
{Object}PassThrough
stream, accessible by fn
.Creates a new writable stream. Just like the one above but for writable streams.
1new lazystream.Writable(function () { 2 return fs.createWriteStream('/dev/null'); 3});
1$ npm install lazystream --save 2lazystream@1.0.1 node_modules/lazystream 3└── readable-stream@2.0.5
readable-stream
2.x.Fork it, branch it, send me a pull request. We'll work out the rest together.
Chris Talkington and his node-archiver for providing a use-case.
Copyright (c) 2013 J. Pommerening, contributors.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 1/25 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2025-06-23
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More