fix(nuxt): disable payload extraction for spa generated pages

[pi0]

🔗 Linked issue

https://github.com/nuxt/framework/discussions/7513#discussioncomment-3649155

❓ 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

SPA pages have no actual payload data (other than initial state).

This also fixes issue for special spa (index.html, 200.html and 404.html) routes.

📝 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	c7df6cb
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/6322d4a8aa6ec60008023253

[danielroe]

Looks good to me. Unless we can imagine a nitro plugin injecting initial info into a payload?

What about checking whether there is content in the payload?

[pi0]

Looks good to me. Unless we can imagine a nitro plugin injecting initial info into a payload?

That is still considered the initial state of the page. What we extract to the _payload.js are data and state keys which are nuxt-app state during SSR.

If Nitro plugins extend anything in the payload, it will be ignored by SPA renderer (following up with another PR to change it). But this is a rare and new usecase for prerendering spa with payload support.