perf: keep document-drive state in shallowRef and prefetch pages/components

[danielroe]

🔗 Linked issue

#2100

❓ 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

This PR implements two changes to speed up the experience on document-driven sites. It should be considered a proof-of-concept and likely warrants further testing.

1. First, we take advantage of the new rich JSON payloads to avoid having fully reactive page data. For deeply nested arrays of objects, this is likely to make a huge performance impact.

2. Second, we preload content queries and the components used on those pages (if the body attribute is present).

In order to enable testing this out on a large site/codebase, I've deployed a patched version of nuxt content:

• without changes: https://nuxt.com/docs
• with changes: https://nuxt-website-idcnshvbq-nuxt-js.vercel.app/docs

(Bear in mind that to test out the document driven changes you will need to stay within the /docs subpath as other pages do not use this strategy and will not be affected by these improvements.)

📝 Checklist

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

[netlify]

✅ Deploy Preview for nuxt-content canceled.

Name	Link
🔨 Latest commit	46c0dbe
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt-content/deploys/649ac056de23ef0008a0ec44

[farnabaz]

Thanks

[rikzwarthoff]

@danielroe @farnabaz @Atinux, Hi guys looks like this is causing some problems. It's also prefetching urls that are relative but external to the application. #2336