npmpackage.info

set-blocking

set blocking stdio and stderr ensuring that terminal output does not truncate

2.0.0

ISC

JavaScript

215.00 B

6,150,829,659 3.4

Installations

npm install set-blocking

Score

98.9

Supply Chain

61.9

Quality

75.1

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

1

Total

9

Closed

1

Merged

7

Issues

Open

2

Total

6

Closed

4

Releases

Unable to fetch releases

Contributors

View all 13 contributors

Developer

yargs

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

Typescript Support

No

Node Version

0.12.7

NPM Version

2.11.3 Statistics

37 Stars

13 Commits

11 Forks

10 Watching

3 Branches

13 Contributors

Updated on 17 May 2024

Bundle Size

307.00 B

Minified

215.00 B

Minified + Gzipped

Bundlephobia

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

6,150,829,659

Last day

-2.2%

5,981,323

Compared to previous day

Last week

5.2%

33,651,893

Compared to previous week

Last month

24.5%

128,210,181

Compared to previous month

Last year

-1.5%

1,279,423,369

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

chai coveralls mocha nyc standard standard-version

Versions

set-blocking

Set blocking stdio and stderr ensuring that terminal output does not truncate.

1const setBlocking = require('set-blocking')
2setBlocking(true)
3console.log(someLargeStringToOutput)

Historical Context/Word of Warning

This was created as a shim to address the bug discussed in node #6456. This bug crops up on newer versions of Node.js (0.12+), truncating terminal output.

You should be mindful of the side-effects caused by using set-blocking:

If your module sets blocking to true, it will affect other modules consuming your library. In yargs we only call setBlocking(true) once we already know we are about to call process.exit(code).
This patch will not apply to subprocesses spawned with isTTY = true, this is the default spawn() behavior.

License

ISC

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

License

Determines if the project has defined a license.

3

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

Score

3.4

/10

Last Scanned on 2024-11-18

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

Other packages similar to set-blocking

@types/set-blocking

2.0.2

TypeScript definitions for set-blocking

blocking-proxy

1.0.1

WebDriver Proxy for testing rich clients. It block certain calls until Angular is done updating the page under test.

workerpool

9.2.0

Offload tasks to a pool of workers on node.js and in the browser

blocking-elements

0.1.1

A polyfill for the proposed blocking elements stack API