nuxt4-patterns

Topics in the source

• Nuxt 4 Patterns
• When to Activate
• Hydration Safety
• Data Fetching
• Route Rules
• Lazy Loading and Performance
• Review Checklist

Use when building or debugging Nuxt 4 apps with SSR, hybrid rendering, route rules, or page-level data fetching. Hydration mismatches between server HTML and client state Route-level rendering decisions such as prerender, SWR, ISR, or client-only sections Performance work around lazy loading, lazy hydration, or payload size Page or component data fetching with useFetch, useAsyncData, or $fetch Nuxt routing issues tied to route params, middleware, or SSR/client differences Keep the first render deterministic. Do not put Date.now(), Math.random(), browser-only APIs, or storage reads directly into SSR-rendered template state. Move browser-only logic behind onMounted(), import.meta.client, ClientOnly, or a .client.vue component when the server cannot produce the same markup. Use Nuxt's useRoute() composable, not the one from vue-router. Do not use route.fullPath to drive SSR-rendered markup. URL fragments are client-only, which can create hydration mismatches. Treat ssr: false as an escape hatch for truly browser-only areas, not a default fix for mismatches. Prefer await useFetch() for SSR-safe API reads in pages and components. It forwards server-fetched data into the Nuxt payload and

This is an excerpt. Refer to the complete source and its current requirements.