fosteric
/
Shared-Travel-Map-Front-End
Suivre 1
Favoriser 0
Bifurcation 0
Code Tickets 0 Demandes d'ajout 0 Versions 0 Wiki Activité
4 Révisions
3 Branches
Aborescence: cb8aa624de
Branches Tags
${ item.name }
Créer la branche ${ searchTerm }
de 'cb8aa624de'
${ noResults }
Shared-Travel-Map-Front-End/node_modules/set-blocking
Eric Foster 35b96bc934 initial commit il y a 6 ans
..
CHANGELOG.md initial commit il y a 6 ans
LICENSE.txt initial commit il y a 6 ans
README.md initial commit il y a 6 ans
index.js initial commit il y a 6 ans
package.json initial commit il y a 6 ans

README.md

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