Tabs warning Computed is still dirty after getter evaluation

[ThomasWT]

Environment

• Operating System: Linux
• Node Version: v18.18.0
• Nuxt Version: 3.10.2
• CLI Version: 3.10.1
• Nitro Version: 2.8.1
• Package Manager: [email protected]
• Builder: -
• User Config: devtools, modules
• Runtime Modules: @nuxt/[email protected]
• Build Modules: -

Version

v2.13.0

Reproduction

https://stackblitz.com/edit/nuxt-starter-d5gcpn

Description

Using the tabs component throws a warning in the console, client side seeming to slow down the clientside hydration

vue.js:288 [Vue warn] Computed is still dirty after getter evaluation, likely because a computed is mutating its own dependency in its getter. State mutations in computed getters should be avoided. Check the docs for more details: https://vuejs.org/guide/essentials/computed.html#getters-should-be-side-effect-free

Additional context

No response

Logs

vue.js:288 [Vue warn] Computed is still dirty after getter evaluation, likely because a computed is mutating its own dependency in its getter. State mutations in computed getters should be avoided.  Check the docs for more details: https://vuejs.org/guide/essentials/computed.html#getters-should-be-side-effect-free

[benjamincanac]

This is a warning that was added in Vue v3.4.19, and an issue has already been created in Headless UI: tailwindlabs/headlessui#2985. We cannot do much about it but to wait for a fix in Headless UI.

[GalacticHypernova]

@benjamincanac does this mean this can be closed with the release of V3 soon?

[benjamincanac]

I guess so as we don't have control over this since it's related to Headless UI!