Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

yargs/set-blocking

Open more actions menu

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

13 Commits
13 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

set-blocking

Build Status NPM version Coverage Status Standard Version

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

const setBlocking = require('set-blocking')
setBlocking(true)
console.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

About

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

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages

Morty Proxy This is a proxified and sanitized view of the page, visit original site.