combination of nuxt-typed-router and vuestic breaks the auto-import / component resolution of Volar

[thunfisch987]

Hi,
when using nuxt-typed-router and vuestic (@vuestic/nuxt) together the auto-imports / component resolution of Volar breaks.
It only works when implicitly importing every component.
This is only a problem with Volar, nuxt dev and so on still works.
It still works when only using one of them, but breaks when using both.
How can i get more information about why it breaks?
Should i rather only ask in the repository of Volar?

[thunfisch987]

It works when reloading VSCode but as soon as you change something in the file or go to another file it breaks:

changing something:

implicitly importing the component

[thunfisch987]

#70 probably/maybe fixes this, i'm gonna test later

[victorgarciaesgi]

Yep was thinking it could be related, tell me if it fixes your problem!

[thunfisch987]

It's fixed! Thanks @mahdiboomeri !

[thunfisch987]

tried the 3.0.0 version, it's back again.
might be because of the Route path autocomplete

[thunfisch987]

dev server runs fine, but the types aren't working

[victorgarciaesgi]

Arrg this one is so frustrating. I had to revert to @vue/runtime-core because vue-router is using it too and breaking all other typings with it. I will see how to correct this nicely

[victorgarciaesgi]

You can try v3.0.1, reverted it to 'vue'

[thunfisch987]

That works!