Daniel Roe
Daniel Roe
Even if it's a current dependency of nuxt, you should not rely on implicit dependencies.
@flapili that's exactly the plan! ... and why that directory exists š - see https://github.com/nuxt/cli/pull/678.
Do you have any system-wide proxy configuration?
Would you provide a reproduction please, and some more info on what is broken? Using this command in the playground of this module works fine for me.
https://github.com/fi3ework/vite-plugin-checker/tree/main/playground/biome-default
iām happy to investigate, but i need a reproduction and more information, please š
When navigating on client-side, there are two 'forks' of a suspense tree. One fork remains on the page displaying the old route. Inside this page the route remains the 'old'...
This could probably be solved in pinia Nuxt module by calling actions with root Vue context rather than component context. I think the current behaviour on the Nuxt end is...
@manafatech that doesn't sound like the same issue, which is a bug related to pinia
this should have been resolved in https://github.com/nuxt/nuxt/pull/24673.