Nuxt 3.15.1 breaks the module

[TheDutchCoder]

Environment

---

• Operating System: Darwin
• Node Version: v20.13.0
• Nuxt Version: 3.15.1
• CLI Version: 3.17.2
• Nitro Version: 2.10.4
• Package Manager: npm@10.5.2
• Builder: -
• User Config: default
• Runtime Modules: @nuxt/eslint@0.7.4, nuxt-open-fetch@0.9.5, @nuxtjs/i18n@9.1.1, nuxt-jsonld@2.1.0, @nuxtjs/device@3.2.4, @nuxtjs/robots@5.1.0, @vueuse/nuxt@12.3.0, @sidebase/nuxt-auth@0.9.4, @vesp/nuxt-fontawesome@1.1.0
• Build Modules: -

---

Reproduction

N/A

Describe the bug

We upgraded to Nuxt 3.15.1, and since then our useThing composable throw hydration errors when fetching data and we have to rely on a custom useAsyncData implementation, using $thing.

Under the hood, useThing should just be useAsyncData('key', $thing() => {}), correct?

So maybe something changed slightly in Nuxt that breaks this implementation?

We've debugged this a bit, and it turns out that the server-side fetch is correct, but initially the client-side one is null for an instant.
You can see this by using an immediate watcher on the data.

Additional context

No response

Logs

No response

[ReWWeR]

Got the same issue. Wrapping everything in custom useAsyncData helps, but I've got a lot of not wrapped API calls so it is not solution for me.

Noticed that problem can be somehow related to payload.data key generation, cause it API called twice (on SSR and on front-end) with different keys.

[jonkri]

It may not be related but I did get a momentary null value here: #62.