Robbert van Mourik
Robbert van Mourik
I agree with you on that
@Jamiewarb I am experiencing the same, did you find any other solutions besides importing it with an alias.
@Deuchnord Is there any ETA for this feature? Would really love to use it :-)
Don't now if it is helpful, but I experienced some similar errors while developing our app. In the end it was caused by a transition component as the root component...
> @rvmourik is on the right track, I went ahead and recreated the [``](https://github.com/nuxt/framework/blob/main/packages/nuxt3/src/pages/runtime/page.ts) component, when I remove the [``](https://github.com/nuxt/framework/blob/main/packages/nuxt3/src/pages/runtime/page.ts#L31) before the `` the error does not pop up, but...
> > i created a new nuxt application and transferred my files to the new application following the rules from the nuxt3 docs. problem fixed. > > how ? make...
I have something related, when I use the route.name in a computed variable OR use the route(.name) in a watch function it doesn't get triggered after navigating. When I output...
> I have something related, when I use the route.name in a computed variable OR use the route(.name) in a watch function it doesn't get triggered after navigating. > >...
Is this already possible?
Hi @keremciu That's nice to here, can you quickly tell what the current solution is until there is a new version of the plugin?