-
Notifications
You must be signed in to change notification settings - Fork 914
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vue-loader errored when html-loader is defined BEFORE it in webpack 5 configuration. #1625
Comments
It is a bug indeed. |
When you use "webpack v5.0.0", if you encounter "error error: [vueloaderplugin error] no matching use for Vue loader is found. Make sure the rule matching. Vue files include Vue loader in its", If other loaders appear before "Vue loader", for example, "HTML loader" appears before "Vue loader", then just add an "enforce" option in the rules of "HTML loader", and its value is the string "post". In this way, the original loader can be used normally without changing the order of the original loader. module: { // first loader // other loader... { ], |
Today, while updating the configuration of webpack 5, I explored this problem and verified that this method is ok. |
This adds a check so that only rules that only match foo.vue.html and not foo.html are ignored. Resolves vuejs#1625
This adds a check so that rules that match foo.vue.html but *also* foo.html are ignored. Resolves vuejs#1625
This adds a check so that rules that match foo.vue.html but *also* foo.html are ignored. Resolves vuejs#1625
Version
15.8.3
Reproduction link
https://github.com/ryanelian/vue-loader-bug
Steps to reproduce
Add this line before vue-loader in webpack 5 configuration.
What is expected?
No error.
What is actually happening?
⬢ webpack: Error: [VueLoaderPlugin Error] No matching use for vue-loader is found.
Make sure the rule matching .vue files include vue-loader in its use.
This is almost exactly the same as a past issue: #1246
But this time it's webpack 5.
The text was updated successfully, but these errors were encountered: