bernhard
/
freifunk-app
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
This app provides monitoring and information features for the common freifunk user and the technical stuff of a freifunk community. Code base is taken from a TUM Practical Course project and added here to see if Freifunk Altdorf can use it. https://www.freifunk-altdorf.de
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
3 Commits
1 Branch
0 Tags
59 MiB
 
 
 
 
Branch: master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
freifunk-app/node_modules/set-blocking
Bernhard Blieninger fc05486403
initial commit taken from gitlab.lrz.de 		6 years ago
..
CHANGELOG.md initial commit taken from gitlab.lrz.de 6 years ago
LICENSE.txt initial commit taken from gitlab.lrz.de 6 years ago
README.md initial commit taken from gitlab.lrz.de 6 years ago
index.js initial commit taken from gitlab.lrz.de 6 years ago
package.json initial commit taken from gitlab.lrz.de 6 years ago

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