Yarn verbose & keep output #1036
Labels
Comments
|
See also the notes here: lovell/sharp#1942 |
acburdine
pushed a commit
that referenced
this issue
Nov 4, 2019
refs #1036 - use verbose option with yarn when verbose is enabled for main command
acburdine
added a commit
to acburdine/Ghost-CLI
that referenced
this issue
Nov 4, 2019
refs TryGhost#1036 - move verbose arg into yarn util - report stderr to observer on verbose
acburdine
added a commit
that referenced
this issue
Nov 4, 2019
refs #1036 - move verbose arg into yarn util - report stderr to observer on verbose
|
Our bot has automatically marked this issue as stale because there has not been any activity here in some time. The issue will be closed soon if there are no further updates, however we ask that you do not post comments to keep the issue open if you are not actively working on a PR. We keep the issue list minimal so we can keep focus on the most pressing issues. Closed issues can always be reopened if a new contributor is found. Thank you for understanding 🙂 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ghost relies on binary dependencies being installed. ATM, even with the
--verboseflag we don't get to see the output from yarn, that would be helpful when debugging issues.Passing the
--verboseflag to yarn results in a lot of output, and tbh we need to record this even if the user doesn't supply the--verboseflag.I suggest we store the output from yarn in a log file?
The text was updated successfully, but these errors were encountered: