webpackAlertFilters #24
Open
Conversation
This file contains hidden or 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
… version from npm
The debug instructions didn't work (anymore). Changed them to something that works.
This was introduced by commit 93f7830 and that was presumably unintentional.
…ringstringstring Removing 'string' suffix on each error line.
Conflicts: npm-shrinkwrap.json package.json
…warnings and soft errors.
…webpackAlertFilters.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Prerequisites
Description
Adding support to suppress webpack soft errors and CriticalDependenciesWarnings.
Note: this affects anyone who uses
webpackWarningFiltersin theirjester.json.Their existing filter config will do nothing until they've migrated to the new
webpackAlertFilters.Test instructions
npm linkfrom ggze to your jester-checkout.