nuxt4-patterns

Use when building or debugging Nuxt 4 apps with SSR, hybrid rendering, route rules, or page-level data fetching. Prefer routeRules in nuxt.config.ts for rendering and caching strategy: Pick route rules per route group, not globally. Marketing pages, catalogs, dashboards, and APIs usually need different strategies. - 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.