Michael Freno
7c684a42cc
- Consolidated duplicate UndoManagers to single instance - Fixed connection promise to only resolve on 'connected' status - Fixed WebSocketProvider import (WebsocketProvider) - Added proper doc.destroy() cleanup - Renamed isPresenceInitialized property to avoid conflict Co-Authored-By: Paperclip <noreply@paperclip.ing>
set-blocking
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 callsetBlocking(true)once we already know we are about to callprocess.exit(code). - this patch will not apply to subprocesses spawned with
isTTY = true, this is the defaultspawn()behavior.
License
ISC