AeThex-Labs/AeThex-Engine-Core
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2
AeThex-Engine-Core/services/auth-service/node_modules/set-blocking/README.md
mrpiglr 190b6b2eab
Some checks are pending
Build AeThex Engine / build-windows (push) Waiting to run
Details
Build AeThex Engine / build-linux (push) Waiting to run
Details
Build AeThex Engine / build-macos (push) Waiting to run
Details
Build AeThex Engine / create-release (push) Blocked by required conditions
Details
Deploy Docsify Documentation / build (push) Waiting to run
Details
Deploy Docsify Documentation / deploy (push) Blocked by required conditions
Details
chore: sync local changes to Forgejo
2026-03-13 00:37:06 -07:00

1.5 KiB
Raw Blame History

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