Skip to content
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 3] warning (deprecation COMPILER_V_BIND_OBJECT_ORDER) #283

Closed
magFixCorp opened this issue Jul 8, 2022 · 1 comment · Fixed by #284 · May be fixed by Matrix-Biz-Nexus-Inc/Current-Backend-Final#2
Closed

[Vue 3] warning (deprecation COMPILER_V_BIND_OBJECT_ORDER) #283

magFixCorp opened this issue Jul 8, 2022 · 1 comment · Fixed by #284 · May be fixed by Matrix-Biz-Nexus-Inc/Current-Backend-Final#2

Comments

@magFixCorp
Copy link

I am migrating my project from Vue2 to Vue3. Everything went successful. The only thing that I am getting as a warning is from this library.

 warning  in ./node_modules/vue-material-design-icons/InformationOutline.vue?vue&type=template&id=456649a2

Module Warning (from ./node_modules/@vue/cli-service/node_modules/vue-loader/dist/templateLoader.js):
(Emitted value instead of an instance of Error) (deprecation COMPILER_V_BIND_OBJECT_ORDER) v-bind="obj" usage is now order sensitive and behaves like JavaScript object spread: it will now overwrite an existing non-mergeable attri
bute that appears before v-bind in the case of conflict. To retain 2.x behavior, move v-bind to make it the first attribute. You can also suppress this warning if the usage is intended.

The solution seems easy, just move the v-bind='$attrs' in the template as a first argument and this warning will be fixed

Regards
Nik

@magFixCorp magFixCorp changed the title Vue 3 warning Vue 3 warning (deprecation COMPILER_V_BIND_OBJECT_ORDER) Jul 8, 2022
@magFixCorp magFixCorp changed the title Vue 3 warning (deprecation COMPILER_V_BIND_OBJECT_ORDER) [Vue 3] warning (deprecation COMPILER_V_BIND_OBJECT_ORDER) Jul 8, 2022
@magFixCorp
Copy link
Author

magFixCorp commented Jul 13, 2022

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant