limepot-xyz/BETA/mybulma/node_modules/set-blocking
LimePot 76722fec47 Beta Site
Going to slowly work on a Bulma site, which will end up being the main site.

Currently under the /BETA/ folder so Alpha site will still be main site.
2022-12-20 16:23:37 -07:00
..
CHANGELOG.md Beta Site 2022-12-20 16:23:37 -07:00
index.js Beta Site 2022-12-20 16:23:37 -07:00
LICENSE.txt Beta Site 2022-12-20 16:23:37 -07:00
package.json Beta Site 2022-12-20 16:23:37 -07:00
README.md Beta Site 2022-12-20 16:23:37 -07: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