Robin
Robin
I am not sure if this is what we want for our ref composables. Passing a ref/reactive to `ref()` does normally return the ref/reactive itself directly. Perhaps we should consider...
I see. However, I think we should only document that this function is shallow, rather than the reactive workaround.
https://github.com/bendotcodes/cookies/pull/867#discussion_r2162126914 Now its confirmed that there are no relevant breaking changes. I think we should go for `^7 || ^8`
I think this might be related to or even a duplicate of https://github.com/nuxt/nuxt/issues/32102
This whole `watch: false`/manual mode originates from:  (By the way, the example link no longer exists.)
+ if you try to use the secord input, it will always use the values of the first. (adjusted the test too)
> [@OrbisK](https://github.com/OrbisK) I’m still experiencing the issue in version 4.2.1 yes. This is currently intended behaviour
Could you please try updating both `vue-tsc` and `typescript` to the latest versions?
> Using VueUse's version nothing happened during SSR when I needed to assign a different value to a query param, but if you think I have missed anything, feel free...
I think there is currently no way to prevent this. NuxtUI [exposes the `$el`](https://github.com/nuxt/ui/blob/db73765d7ab7af6ae5c71d85057f66eb2e422754/src/runtime/components/Tree.vue#L245-L249) manually. But not sure if this is the best solution. I think if you want multiple...