Files
SkyArtShop/backend/node_modules/set-blocking
Local Server 8bb6430a70 Website restoration: Node.js backend, restored design, GitHub sync disabled
- Replaced broken .NET backend with Node.js/Express
- Restored original website design with purple gradient hero
- Updated homepage and shop pages with Bootstrap 5 responsive design
- Disabled GitHub remote sync - all code now stored locally only
- Created backup scripts and documentation
- All changes saved on Ubuntu server at /var/www/SkyArtShop
2025-12-13 17:53:34 -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