-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
Unable to configure CLI on Vue 3 to fix warning from web components #5610
Comments
I've found the fix. The Vue CLI config is: module.exports = {
chainWebpack: config => {
config.module
.rule('vue')
.use('vue-loader')
.loader('vue-loader')
.tap(options => {
options.compilerOptions = {
...(options.compilerOptions || {}),
isCustomElement: tag => /^x-/.test(tag)
};
return options;
});
}
}; And in addition, I needed to install the beta version of vue-loader |
While the config by @BlackSonic worked somewhat, there was one error I was getting::
To fix this, just replace the
|
This is not works for me at all. It compiles project, but noisy messages |
@BlackSonic's solution worked like a charm for me to ignore I did get some errors when initially I copied/pasted @BlackSonic solution--not sure exactly what I changed but the following is working for me:
This is basically the same code as originally posted, with some other options shown only for context. But I think a lot of people are specifically trying to ignore |
You need to write:
```
...
.loader( require.resolve( "vue-loader-v16" ) )
...
```
until `vue-loader` v16 will be released.
|
Version
4.4.5
Reproduction link
https://github.com/blacksonic/todomvc-vue-composition-api
Environment info
Steps to reproduce
at
at
What is expected?
By modifying the webpack config the warning can be solved, but unable to reach the vue compiler config
What is actually happening?
The warning still remains there
Related issue vuejs/core#1414
I've tried using the official Vue CLI documentation for configuring vue-loader, but no success
https://cli.vuejs.org/guide/webpack.html
The text was updated successfully, but these errors were encountered: