Run & review this pull request in StackBlitz Codeflow.

Walkthrough

This pull request updates Nuxt documentation to reflect changes to getCachedData semantics: the default implementation no longer preserves data across client-side navigations, only providing cached values during SSR hydration or when payloadExtraction is enabled. Docs add an opt-in mechanism to persist client-side data via a custom getCachedData, describe a new ctx.cause parameter (e.g. refresh:manual/refresh:hook) for conditional cache bypassing, and present two caching patterns (cache-until-refresh and stale-while-revalidate) with examples and guidance. Changes touch getting-started, upgrade notes, and composables API docs.

Possibly related PRs

• fix(nuxt): use single synced asyncdata instance per key #31373: Adds the request context parameter to getCachedData (including cause) used for conditional cache logic referenced in the docs.
• fix(nuxt): do not clear data if custom getCachedData is provided #32003: Implements runtime behaviour to preserve cached data when a custom getCachedData is provided, aligning with the documented opt-in caching pattern.
• perf(nuxt): use browser cache for payloads #31379: Introduces purgeCachedData and adjusts payload/static-data caching semantics that the documentation updates describe.

No actionable comments were generated in the recent review. 🎉

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

There is also a related topic that we could cover here:

By default the old keys data is purged on key change. However this does not happen if there is a custom cached function.