Upgrade Webpack to Version 5 #201
Merged
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
alexander-schranz
force-pushed
the
feature/upgrade-webpack-5
branch
from
d64ee3c
to
080c382
Compare
5 tasks
|
Do you need to repush this? |
alexander-schranz
force-pushed
the
feature/upgrade-webpack-5
branch
from
080c382
to
e4c9b06
Compare
alexander-schranz
force-pushed
the
feature/upgrade-webpack-5
branch
from
e4c9b06
to
021c3a6
Compare
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.
What's in this PR?
Upgrade Webpack to Version 5.
Why?
Webpack 4 is outdated and the terser parser did create a lot of problems in the past because it is also outdated.