fix: augment @vue/runtime-core

[danielroe]

resolves nuxt/nuxt#28440

Investigating the type issues in latest vue/vue-router projects, I think we need to augment @vue/runtime-core, as these types will flow 'up' into the vue types (example), but - in some cases - not the other way around (see vuejs/router#2341 and the linked reproduction).

[antfu]

Well, this is so tricky, we moved back and forth so many times:

• fix: drop declare module '@vue/runtime-core' #359
• fix: extends types to vue instead of @vue/runtime-core unplugin/unplugin-vue-components#638
• fix: extend type GlobalComponents in "@vue/runtime-core" unplugin/unplugin-vue-components#344
• fix: router typescript definations related to vue package vuejs/router#2295

After reading nuxt/nuxt#28542 it makes me even more confused. I vaguely remember at some version of Vue we start to recommend always augmenting against vue. Now we are moving back again, or only for certain types?

[danielroe]

I think this is actually my mistake, and the current behaviour is correct. 🤦

[ThomasBerneHCSE]

Then if it is the correct behavior, how do you explain the error some people (like me) encounters in this issue @danielroe: nuxt/nuxt#28440 ? (And stil experiencing the issue in nuxt 3.13.0)

[danielroe]

@ThomasBerneHCSE it requires every library to augment vue and not @vue/runtime-core. If you are using a library that doesn't, its code also needs to be updated.

[ThomasBerneHCSE]

Ok Thanks for the quick answer. It seems to be the case for vuetify. I'm opening an issue on their side.

[douglasg14b]

@ThomasBerneHCSE Can you like the vuetify ticket to this one?

[ThomasBerneHCSE]

It has been fixed in vuetify 3.7.1. Just update to the latest version.