[ChakraLoaderPlugin Error] No matching rule for vue-loader found
See original GitHub issueDescribe the bug
When I upgrade @charkra/ui-nuxt version from 0.0.13
to 0.1.0
--> This had an error.
[ChakraLoaderPlugin Error] No matching rule for vue-loader found.
Please make sure that vue-loader is installed and included in your webpack config.
Expected behavior
I upgrade this package because I want my team work with the new properties CSS like place-content="center space-between"
. So hope you or your team will fix it!
Screenshots
Desktop (please complete the following information):
- OS: MacsOs 10.15.4
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Error: [VuetifyLoaderPlugin Error] No matching rule for vue ...
I'm running `Environment Info: System: OS: freebsd CPU: (4) x64 Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz Binaries: Node: 15.2.0 ...
Read more >VuetifyLoaderPlugin Error No matching rule for vue-loader found
Make sure there is at least one root-level rule that uses vue-loader and VuetifyLoaderPlugin is applied after VueLoaderPlugin. The package.json:
Read more >[VueLoaderPlugin Error] No matching use for vue-loader is ...
Hi there, I am stuck on VueLoaderPlugin problem (Webpack) for quite a while even after googling for hours. Error: [VueLoaderPlugin Error] No ......
Read more >VuetifyLoaderPlugin Error No matching rule for vue-loader ...
Coding example for the question VuetifyLoaderPlugin Error No matching rule for vue-loader found-Vue.js.
Read more >VuetifyLoader plugin problem #632 - Issuehunt
config.js. On compilation, I have this error : Error: [VuetifyLoaderPlugin Error] No matching rule for vue-loader found. Make sure ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hey @harrytran998, @bmulholland!
Solution
@chakra-ui/nuxt@^0.1.0
, In yournuxt.config.js
file, you no longer need to install theChakraLoaderWebpackPlugin
inbuild.extend
option. This handled internally.chakra-loader
package yourself, since it’s an internal dependency for the@chakra-ui/nuxt@^0.1.0
.The cause of the issue After digging into this, I think I realize the cause of this problem. After upgrading
@chakra-ui/nuxt
tov0.1.0
, you needn’t manually setup thechakra-loader
plugin innuxt.config.js
file. I’m not sure why the error comes up if you manually setchakra.config.autoImport: true
and add then proceed to add the plugin in thebuild.extend()
option of thenuxt.config.js
file.Going forward At the time of developing this feature, I didn’t encounter this problem. After seeing the cause of the issue, I can see why this would have been better to instead make a major change in the package versioning. I may do this in the next release to account for this issue. I’m also interesting in hearing feedback around this problem.
So for now I’ll tag it as having a work-around, but will leave the issue open to facilitate this.
@harrytran998 For your project, As a workaround, your team can still use the
place-content
properties by upgrading the@chakra-ui/vue
package independently tov0.6.6