mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-09-30 01:07:01 +08:00
Lorne Mitchell
db3885dd80
This reverts commit 4df552c652.
Reason for revert: Breaks esprima.
Original change's description:
> Updates node_modules and update script
>
> Change-Id: I3fcf49bc416301a030d298cfc48c448bfeba4335
> Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/1878808
> Reviewed-by: Tim van der Lippe <tvanderlippe@chromium.org>
> Reviewed-by: Yang Guo <yangguo@chromium.org>
> Commit-Queue: Paul Lewis <aerotwist@chromium.org>
TBR=yangguo@chromium.org,aerotwist@chromium.org,tvanderlippe@chromium.org
Change-Id: Iad2bcdf98a486476715d1e829cdce450c5f218af
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/1880098
Reviewed-by: Lorne Mitchell <lomitch@microsoft.com>
Commit-Queue: Lorne Mitchell <lomitch@microsoft.com>
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