feat(dev): add loglevel to configure console logging #351
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
|
1 similar comment
Codecov Report
|
6 tasks
|
I don't see why we couldn't have a log level option. Thank you for adding the documentation as well! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
logleveloptionloglevelis"silent"We use this plugin to export a "virtual dependency" in our published modules, so that consumers of our module can override a deep dependency. We then alias the virtual module in Webpack config, not babel config. So we expect the virtual module not to exist at Babel build time.
Your plugin works great (thank you!) but it logs a lot of warnings due to our configuration, so we'd appreciate this option to quiet them.