Drop support for cache-loader on webpack 5+ #603
Conversation
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
|
@Akryum Can you take a look at this PR? Alternatively, we can selectively use cache-loader only if the package is available. Let me know and I can make that change. |
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.
Since the release of webpack 5, cache-loader has been deprecated. It currently continues to work with webpack 5, but it has a peerDependency on webpack 4. This causes installs to fail on newer versions of npm 7.
I have a PR open on vue-cli (which intends to support webpack 5) that drops usage of cache-loader in favor of the new filesystem cache introduced with webpack 5.
The vue-ui package (one of the packages in @vue/cli) depends on this plugin.