glink-website/node_modules/set-blocking
Aravind142857 b700ef7423 Signup added. Backend added
..
CHANGELOG.md Signup added. Backend added
LICENSE.txt Signup added. Backend added
README.md Signup added. Backend added
index.js Signup added. Backend added
package.json Signup added. Backend added

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