fix(nuxt): await asyncData if ssr: false

[danielroe]

🔗 Linked issue

resolvesnuxt/nuxt#13917

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

We should await useAsyncData on initial load if there was no SSR.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[netlify]

✅ Deploy Preview for nuxt3-docs canceled.

Name	Link
🔨 Latest commit	add71fd
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/62724465551325000b619ebe

[pi0]

I was thinking if we could make fix more generic and try to refetch if for any reason key is not in the payload (it can be ssr: false but also timeout for fallback)

[danielroe]

Those are both nice ideas, but we wouldn't want to await on fetch in those cases as it would cause a hydration mismatch. (I think the solution to this bug and those is not connected.)

Can we make that another issue and resolve in future PR? (happy to look at it straight away)