Reinier Kaper

I just ran into this issue in Github workflows as well. Any option to have this looked at?

@arashsheyda thanks, will this break/limit any of the devtools functionality? If so, then that wouldn't be great, of course.

@arashsheyda Ok, then let's leave this open as a bug, because we really would like to be able to use both 😉

Any chance this could be picked up? Can we also remove the "has workaround" label? Disabling devtools is not really a "workaround" imo 😉

I think this is a much deeper issue. When I use `useCookie` in a composable it doesn't even remain reactive within the composable itself, unless I hoist the `useCookie` outside...

@danielroe I do get the "local" version to work in a reproduction, which is interesting as it's the same code we use in our project: https://stackblitz.com/edit/github-1mayxm?file=composables%2FuseBanner.ts But they don't update...

> This is related to the now switched-on `cookieStore` feature. As a workaround, disabling it for now (`experimental.cookieStore` to `false`) should resolve the issue. > > Linking [f597ca59a](https://github.com/nuxt/nuxt/commit/f597ca59a) and #25198...

@danielroe @manniL Here's a simple reproduction, useCookie is broken by default at the moment: https://stackblitz.com/edit/github-ojwre2?file=app.vue Edit: I finally got it working by disabling the `cookiestore` flag. Not sure why it...

@danielroe would you recommend having a "global" file with cookies and their defaults? Because it'll be impossible to tell which useCookie will end up being called "first" if it's just...

It also doesn't work in `` blocks in SFC's