Upgrade clean-webpack-plugin to version 4.0.0 #113
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.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ clean-webpack-plugin (^2.0.1 → ^4.0.0) · Repo
Release Notes
4.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 17 commits:
moved out of alpha, closes #199
Merge pull request #195 from strootje/update-webpack-v5
updated readme, cleaned up code as per PR suggestions
Merge branch 'master' into update-webpack-v5
updated code to not be to strictly typed, webpack fixed their types
Removed @types/webpack dependency. This breaks with webpack 5
fixed lint issue
refactored code to match styling more, updated webpack typings
updated tests to match
peerdependency correction
ran linter and prettier
added related assets (map files) to the cleaning process
updated code, trying to fix tests
Merge pull request #187 from stepbackj/issue-173-fix
update README.md
perf: skip heavy resource webpack stats (#164)
perf: skip heavy resource webpack stats
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands