feat: add a @vue/cli-plugin-webpack-4 package for future use #6144
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
More and more webpack plugins no longer support webpack 4 in their most recent versions. For better webpack 5 compatibility and easier upgrade in the future, we should update these dependencies. So it makes sense to extract webpack-4-specific dependencies and logic to a standalone package. While the task is not that urgent at the moment, and I haven't got the time to complete this refactor, I think we should at least have a placeholder package here, so that users don't have to manually add this dependency in later prerelease versions.
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.
More and more webpack plugins no longer support webpack 4 in their most
recent versions. For better webpack 5 compatibilities and easier upgrades
in the future, we should update these dependencies.
So it makes sense to extract webpack-4-specific dependencies and logic
to a standalone package.
While the task is not that urgent at the moment, and I haven't got the
time to complete this refactor, I think we should at least have a
placeholder package here, so that users don't have to add this
dependency manually in later prerelease versions.
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
Other information: