setup-kubectl/node_modules/set-blocking
github-actions[bot] 7ad2aa66bb
Add node modules and new code for release (#39)
Co-authored-by: tbarnes94 <tbarnes94@users.noreply.github.com>
2022-01-05 11:26:06 -05:00
..
CHANGELOG.md Add node modules and new code for release (#39) 2022-01-05 11:26:06 -05:00
index.js Add node modules and new code for release (#39) 2022-01-05 11:26:06 -05:00
LICENSE.txt Add node modules and new code for release (#39) 2022-01-05 11:26:06 -05:00
package.json Add node modules and new code for release (#39) 2022-01-05 11:26:06 -05:00
README.md Add node modules and new code for release (#39) 2022-01-05 11:26:06 -05:00

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