Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upstandard output is truncated using node v6 #519
Comments
This comment has been minimized.
This comment has been minimized.
|
Wow, that's unfortunate. |
This comment has been minimized.
This comment has been minimized.
|
one work-around to this new node v6 behaviour is to replace process.exitCode = 1
return This allows the process to exit gracefully, without losing any buffered IO, but ironically causes standard to fail every time due to #510 . |
This comment has been minimized.
This comment has been minimized.
|
There's discussion of fixing this bug in Node v6 here: nodejs/node#6456 |
feross
added a commit
to standard/standard-engine
that referenced
this issue
May 16, 2016
feross
closed this
in
standard/standard-engine#108
May 16, 2016
This comment has been minimized.
This comment has been minimized.
|
Turns out this was a pretty easy fix in @75lb If you |
This comment has been minimized.
This comment has been minimized.
|
confirmed.. cheers brother |
This comment has been minimized.
This comment has been minimized.
|
Cheers |
This comment has been minimized.
This comment has been minimized.
|
Wow this is good info to know regarding v6... |
This comment has been minimized.
This comment has been minimized.
|
@Flet Yeah... hoping they find a way to keep writes to stdout async but flush the pending data before exit. |
75lb commentedMay 12, 2016
using node v6, the output from standard is only partially logged to stdout.. it's caused by the new process.exit() behaviour.
for now, i can get the full output by piping to a file or
pbcopy.