Routing, data fetching, state and config, plugins, error handling, SEO and images, rendering strategies, i18n: the app developer's Nuxt.
Pages
- Routing and pagesFile-based routing in Nuxt 4, definePageMeta, layouts, route middleware on server and client, NuxtLink prefetching, typed routes and the route rules that live in Nitro.
- Data fetchinguseFetch, useAsyncData and $fetch, the payload and why data is not fetched twice, keys, options, caching with getCachedData, forwarding headers, interceptors and error handling.
- State and runtime configuseState for SSR-safe shared state, what the payload can serialise, runtimeConfig versus app.config versus environment variables, useCookie, and when a store is the right tool.
- Plugins and auto-importsPlugin order, dependsOn and parallel, providing typed helpers, app hooks, callOnce and onNuxtReady, and how components, composables and utils are scanned and named.
- Error handlingWhere errors happen in a Nuxt app and where they surface — createError and error.vue, fatal versus non-fatal, NuxtErrorBoundary, useAsyncData errors, server route errors, hooks and monitoring.
- SEO, head and mediauseSeoMeta and useHead on Unhead, titles and OG tags, canonical URLs, sitemaps and structured data with the Nuxt SEO modules, and the image, font and script modules that protect LCP and CLS.
- Rendering strategiesUniversal rendering, SPA, prerendering, SWR and ISR per route, client-only and server components, islands, lazy hydration and streaming, and how to choose per route rather than per app.
- InternationalisationThe @nuxtjs/i18n module — routing strategies, lazy-loaded messages, locale detection, SEO tags, formatting with Intl, right-to-left layouts and the hydration trap of a locale that differs between server and client.
Notes for the whole section