Skip to content
set blocking stdio and stderr ensuring that terminal output does not truncate
JavaScript
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
test fix: windows stuff (#10) Dec 18, 2016
.gitignore
.travis.yml chore: update travis config with node LTS & stable (#11) Dec 18, 2016
CHANGELOG.md
LICENSE.txt
README.md
appveyor.yml
index.js
package.json chore(release): 2.0.0 May 17, 2016

README.md

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 effect 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

You can’t perform that action at this time.