LumeWeb
/
bigint-crypto-utils
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
bigint-crypto-utils/node_modules/set-blocking
History
juanelas c29b520108 JS Standard. Some fixes with the test. Better structure 2020-04-06 13:17:22 +02:00
..
CHANGELOG.md JS Standard. Some fixes with the test. Better structure 2020-04-06 13:17:22 +02:00
LICENSE.txt JS Standard. Some fixes with the test. Better structure 2020-04-06 13:17:22 +02:00
README.md JS Standard. Some fixes with the test. Better structure 2020-04-06 13:17:22 +02:00
index.js JS Standard. Some fixes with the test. Better structure 2020-04-06 13:17:22 +02:00
package.json JS Standard. Some fixes with the test. Better structure 2020-04-06 13:17:22 +02:00

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