Allow to supress uglifyjs warnings#4200
Merged
Merged
Conversation
only works if "sourceMap" setting is true
sokra
requested changes
Feb 8, 2017
Member
sokra
left a comment
There was a problem hiding this comment.
Please add an integration test. -> configCases
sokra
approved these changes
Feb 9, 2017
Member
|
Thanks, please also update the documenation. |
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
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.
What kind of change does this PR introduce?
feature
Did you add tests for your changes?
yes
If relevant, link to documentation update:
N/A
Summary
fixes #1496 by adding a
warningsFilterfunction to options for the UglifyJsPlugin that decides which warnings should be shownDoes this PR introduce a breaking change?
No
Other information
The test setup for uglifyJs is a bit messy so i just hacked in two tests. I didnt feel like making sense out of it.