aravind
/
glink-website
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
php
nodejs
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '91702fe33a'
${ noResults }
glink-website/node_modules/set-blocking
History
Aravind142857 b700ef7423 Signup added. Backend added 2 years ago
..
CHANGELOG.md Signup added. Backend added 2 years ago
LICENSE.txt Signup added. Backend added 2 years ago
README.md Signup added. Backend added 2 years ago
index.js Signup added. Backend added 2 years ago
package.json Signup added. Backend added 2 years ago

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