useAsyncData Explained

const { data } = await useAsyncData('posts', () => $fetch('/api/posts'))

// Topic: useAsyncData Explained
const loader = { key: 'posts', cached: true };
console.log(loader.key + ':' + loader.cached);

// Expected Output: posts:true

• 1Use stable keys and return serializable data from the loader. Use the focus terms (useasyncdata, explained, reference UCD073B) to keep this lesson tied to its exact Nuxt.js topic.
• 2Document keyed async data composable for custom loaders with focus terms: useasyncdata, explained, reference UCD073B in the smallest useful page, layout, composable, store, server route, or deployment step.
• 3Represent every loading, success, denied, stale, and failure state that useAsyncData Explained can expose.
• 4Test initial SSR, key changes, refresh, errors, and duplicate requests. Include a check for these focus terms: useasyncdata, explained, reference UCD073B.
• 5Use cache correctness and hydration safety tracked for useasyncdata, explained, reference UCD073B to guide improvements.
• 6Start with clear requirements and one minimal working example.
• 7Use meaningful names that explain business intent.
• 8Keep examples small enough to debug line by line.
• 9Validate input at every trust boundary.
• 10Handle errors explicitly and preserve useful context.
• 11Prefer simple control flow over deeply nested logic.
• 12Separate domain logic from I/O and framework code.
• 13Write tests for normal, boundary, and failure cases.
• 14Review security assumptions before production use.
• 15Measure performance before optimizing.
• 16Document non-obvious decisions close to the code or in project notes.
• 17Use official documentation when behavior is version-specific.
• 18Keep dependencies current and remove unused code.
• 19Avoid hardcoded secrets, credentials, and environment-specific paths.
• 20Log operational events without exposing sensitive data.
• 21Design examples so learners can safely modify and rerun them.
• 22Prefer maintainability over short-term cleverness.