Archived
1
0
This repository has been archived on 2023-05-15. You can view files and clone it. You cannot open issues or pull requests or push a commit.
Files
home-page/node_modules/set-blocking
Sean Edmunds 3e953ad8d2 v1.1 update - stable
this version will run with npm start, but when attempting to run the built version behind nginx, it appears to have issues
2021-12-15 01:48:50 +00:00
..
2021-12-13 17:00:40 -06:00
2021-12-13 17:00:40 -06:00
2021-12-13 17:00:40 -06:00
2021-12-15 01:48:50 +00:00
2021-12-13 17:00:40 -06: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