stale/node_modules/set-blocking
PJ Quirk 0649bd8119
Add support to v1 to connect to GHES (#69)
* Bumping actions/github to 2.2.0 for GHES

* Husky commit correct node modules
2020-05-15 15:25:57 -04:00
..
CHANGELOG.md Add support to v1 to connect to GHES (#69) 2020-05-15 15:25:57 -04:00
LICENSE.txt Add support to v1 to connect to GHES (#69) 2020-05-15 15:25:57 -04:00
README.md Add support to v1 to connect to GHES (#69) 2020-05-15 15:25:57 -04:00
index.js Add support to v1 to connect to GHES (#69) 2020-05-15 15:25:57 -04:00
package.json Add support to v1 to connect to GHES (#69) 2020-05-15 15:25:57 -04: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