![]() | Name | Last modified | Size | Description |
---|---|---|---|---|
![]() | Parent Directory | - | ||
![]() | CHANGELOG.md | a year ago | 718 | |
![]() | LICENSE.txt | a year ago | 731 | |
![]() | README.md | a year ago | 1.5K | 595aea1 more query options + view options [كارل مبارك] |
![]() | index.js | a year ago | 252 | |
![]() | package.json | a year ago | 1.0K | afd0ccc remove unused [كارل مبارك] |
set blocking stdio
and stderr
ensuring that terminal output does not truncate.
const setBlocking = require('set-blocking')
setBlocking(true)
console.log(someLargeStringToOutput)
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
:
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)
.isTTY = true
, this is
the default spawn()
behavior.ISC