</>PackageGraphPackageGraph

stdout-stream

npmv2.0.0

Non-blocking stdout stream

Not recommended for new projects

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

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

    No download data reported for this package yet.

  • FMaintenance: grade F, Failing.

    Last published 1443 days ago.

  • AWeight: grade A, Excellent.

    Pulls in 1 transitive package, about 4.3 KB installed (at least — some of the tree is still being crawled).

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • 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 stdout-stream to a project.

1
Direct dependencies

Runtime packages this one declares itself.

1
Total installed

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

4.3 KB
Install size

Unpacked size of this package plus its entire runtime tree.

1
Tree depth

Longest resolved dependency chain below this package.

Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.

Compatibility

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

Quick start

A usage example from the stdout-stream README.

jsFull README ↗
console.error('start');
process.stdout.write(new Buffer(1024*1024));
console.error('end');

Dependencies

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

Runtime (1)

readable-stream ^4.1.0

Dev (1)

tape ^5.5.3

Used by

Popular packages that depend on stdout-stream.

node-sassnpm

Wrapper around libsass

↓ 811.9K/wk◈ 0 dependents⚖ MITdeprecated

Relationship graph

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

node-sassstdout-stream
stdout-stream dependencies dependents

Frequently installed together

eslintnpm

An AST-based pattern checker for JavaScript.

↓ 145.9M/wk◈ 268 dependents⚖ MITTS
make-fetch-happennpm

Opinionated, caching, retrying fetch client

↓ 43.3M/wk◈ 1 dependents⚖ ISC
nannpm

Native Abstractions for Node.js: C++ header for Node 0.8 -> 26 compatibility

↓ 31.2M/wk◈ 2 dependents⚖ MIT
true-case-pathnpm

Given a possibly case-variant version of an existing filesystem path, returns the case-exact, normalized version as stored in the filesystem.

↓ 2M/wk◈ 1 dependents⚖ Apache-2.0
sass-graphnpm

Parse sass files and extract a graph of imports

↓ 780.2K/wk◈ 1 dependents⚖ MIT
async-foreachnpm

An optionally-asynchronous forEach with an interesting interface.

↓ 745.8K/wk◈ 1 dependents
meownpm

CLI app helper

↓ 0/wk◈ 1 dependents⚖ MIT
cross-spawnnpm

Cross platform child_process#spawn and child_process#spawnSync

↓ 0/wk◈ 8 dependents⚖ MIT
globnpm

the most correct and second fastest glob implementation in JavaScript

↓ 0/wk◈ 35 dependents⚖ BlueOak-1.0.0TS
gazenpm

A globbing fs.watch wrapper built from the best parts of other fine watch libs.

↓ 0/wk◈ 1 dependents⚖ MIT
lodashnpm

Lodash modular utilities.

↓ 0/wk◈ 18 dependents⚖ MIT

Release history

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

Recent versions of stdout-stream
VersionPublishedSizeLicense
2.0.0latest4 years ago4.3 KBMIT
1.4.18 years ago4.4 KBMIT
1.4.011 years ago—MIT
1.3.012 years ago—MIT
1.2.012 years ago—MIT
1.1.012 years ago—MIT
1.0.512 years ago—MIT
1.0.412 years ago—MIT
1.0.312 years ago—MIT
1.0.212 years ago—MIT
1.0.112 years ago—MIT
1.0.012 years ago—MIT

Overview

stdout-stream is an npm package that non-blocking stdout stream. It has 1 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 non-blocking stdout stream 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

mafintosh

Frequently asked questions

Should I use stdout-stream?

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

How do I install stdout-stream?

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

How many dependencies does stdout-stream have?

stdout-stream declares 2 direct dependencies and pulls in 1 packages in total once its runtime tree is resolved totalling about 4.3 KB on disk.

What license is stdout-stream released under?

stdout-stream is distributed under the MIT license.

How popular is stdout-stream?

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

Is stdout-stream still maintained?

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

Does stdout-stream run install scripts?

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