https://github.com/adrienbaron/vuetify-bug-theme-nuxt-i18n
This is also broken in Nuxt Edge.
I initially thought it was a bug in Vuetify 1.2.x and opened an issue there: https://github.com/vuetifyjs/vuetify/issues/5032.
It turns out that Nuxt is missing a merge strategy for the head hook.
Nuxt should probably declare this merge strategy to avoid those kind of conflicts:
Vue.config.optionMergeStrategies.head = Vue.config.optionMergeStrategies.data
@adrienbaron Could you add a PR for that? :relaxed:
Ok, so after trying to get this to work, I noticed that my fix actually breaks some behavior of Vue Meta (thank you unit tests ^^).
I wonder if this fix should not be in Vue Meta, but I just learned about it today so I'm not sure.
From reading their doc, it seems to already deal with merging info between parent and child components. Maybe they just don't support merging info from mixins?
I think vue-meta does not support merging from mixins indeed, I am open for any help on improving vue-meta @adrienbaron
Will be resolved with https://github.com/declandewet/vue-meta/pull/262
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Most helpful comment
I think vue-meta does not support merging from mixins indeed, I am open for any help on improving vue-meta @adrienbaron