Toms Dobrovoļskis

@danielroe Is it really the same Vue bug as in #22353? I don't use multiple layouts there and still get this error.

@danielroe What would be the right way to fix the issue I'm dealing with (redirecting to the same route but adding/changing a query param in setup when an API error...

@quroom, do you still use the workaround you provided here and did it solve your issue? I am facing the same issue and I am looking for a fix.

I struggled with this while working on a Nuxt 3 project using Vitest, nuxt-vitest. While tinkering around I stumbled upon a combination that works for me. Here is what worked...

While fiddling around with the `registerEndpoint` source code I came upon a solution of some kind which solved my problem and might serve as an idea worth adding: ``` function...

Facing the same issue, Lighthouse reports this: `[aria-*] attributes do not match their roles` Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes....

These changes would be greatly appreciated as the `destroy()` function in `src/composables/useSlider.js` calls `slider$.value.off()` but `slider$.value` is sometimes non existent.

Would also like the ability to disable the spring effect on default presets.

Noticed the same issue on `"nuxt": "4.1.2"` and `"@sentry/nuxt": "10.12.0"`. After rollback to `"@sentry/vue": "10.12.0"`, the memory leak issue seems to be gone.

@s1gr1d `@sentry/vue` was set up as a Nuxt plugin that runs only on the client side. `@sentry/nuxt` was set up according to the manual setup guide here: https://nuxt.com/modules/sentry.