Daniel Roe
Daniel Roe
Up-to-date sandbox: https://stackblitz.com/edit/github-awmnqa. (Note that this is working fine with webpack.)
@antlionguard Would you provide a simple reproduction showing how a route ends up being cached? Have you enabled nitro caching on any routes?
If you are not using nitro then this is almost certainly not an issue with Bridge. But will happily look at reproduction just in case!
Ah. Wrapping in `` doesn't mean that those components don't load on the server - it only means that no HTML is emitted. They may all still run. So if...
That sounds cross-request state pollution and I would investigate pinia in that case. It doesn't _sound_ like a Bridge issue.
It shouldn't be something you need to do. Both Nuxt + pinia should ensure this. Would you create a minimal reproduction so I can look into it further? :pray:
The issue is that you are defining your state outside of the factory function: ```js const InitialAuthState: AuthState = { token: '', }; export const useAuthStore = defineStore('auth', { state:...
Yes, I can confirm the issue persists (**[reproduction](https://stackblitz.com/edit/github-xzq91u)** - and [working without Bridge](https://stackblitz.com/edit/github-xzq91u-mdlcrp?file=package.json)), though a workaround is to enable vite mode @tylerforesthauser: ```js import { defineNuxtConfig } from '@nuxt/bridge' export...
Ah, yes. This was an upstream change in `unimport`. Please see [this migration guide](https://github.com/nuxt/framework/pull/6025). It is for Nuxt 3 but applies in this case.