fix: cleanAfterEveryBuildPatterns negative patterns #112
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
…m being removed via negative pattern match
Codecov Report
@@ Coverage Diff @@
## master #112 +/- ##
=========================================
+ Coverage 98.64% 98.7% +0.05%
=========================================
Files 1 1
Lines 74 77 +3
Branches 25 26 +1
=========================================
+ Hits 73 76 +3
Misses 1 1
Continue to review full report at Codecov.
|
|
done! good stuff ✨ |
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.
Adding negative patterns to
cleanAfterEveryBuildPatternswas not excluding matching stale webpack assets. This is an issue when using this plugin with something like copy-webpack-plugin that does not persist with webpack's reported assets.I think we should release an update to npm after merging this.