Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(gatsby): Respect VERBOSE env var #29708

Merged
merged 4 commits into from
Feb 23, 2021

Conversation

sidharthachatterjee
Copy link
Contributor

@sidharthachatterjee sidharthachatterjee commented Feb 23, 2021

For gatsby develop

Incremental Builds supports this so we want feature parity for Preview

This depends on #29707

@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Feb 23, 2021
@sidharthachatterjee sidharthachatterjee removed the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Feb 23, 2021
@sidharthachatterjee sidharthachatterjee changed the title feat(gatsby): Respect GC_VERBOSE env var feat(gatsby): Respect VERBOSE env var Feb 23, 2021
pieh
pieh previously approved these changes Feb 23, 2021
@sidharthachatterjee sidharthachatterjee added the bot: merge on green Gatsbot will merge these PRs automatically when all tests passes label Feb 23, 2021
@gatsbybot gatsbybot merged commit 97d6d3e into master Feb 23, 2021
@gatsbybot gatsbybot deleted the feat/enable-verbose-logging-for-gc branch February 23, 2021 16:22
@KyleAMathews
Copy link
Contributor

A bit late jumping in here but why don't we solve this more generally and let people set the logging level for when we create the CLI?

process.env.gatsby_log_level = argv.verbose ? `verbose` : `normal`
report.verbose(`set gatsby_log_level: "${process.env.gatsby_log_level}"`)

@KyleAMathews
Copy link
Contributor

e.g. LOG_LEVEL=verbose

ascorbic pushed a commit that referenced this pull request Feb 23, 2021
* Respect GC_VERBOSE env var

* Switch to VERBOSE

* Support VERBOSE in build as well

Co-authored-by: gatsbybot <mathews.kyle+gatsbybot@gmail.com>
(cherry picked from commit 97d6d3e)
@sidharthachatterjee
Copy link
Contributor Author

@KyleAMathews We could do that. But I just added this for feature parity for Incremental Builds and Preview. The latter didn't support verbose logging at all.

@gatsbybot
Copy link
Collaborator

gatsbybot commented Feb 24, 2021 via email

ascorbic added a commit that referenced this pull request Feb 24, 2021
* feat(gatsby): Respect VERBOSE env var (#29708)

* Respect GC_VERBOSE env var

* Switch to VERBOSE

* Support VERBOSE in build as well

Co-authored-by: gatsbybot <mathews.kyle+gatsbybot@gmail.com>
(cherry picked from commit 97d6d3e)

* Add back chalk

Co-authored-by: Sidhartha Chatterjee <me@sidharthachatterjee.com>
Co-authored-by: Matt Kane <matt@gatsbyjs.com>
@ascorbic
Copy link
Contributor

Published in gatsby@2.32.6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bot: merge on green Gatsbot will merge these PRs automatically when all tests passes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants