Startup sequence, Nitro and h3, the unjs toolbelt, auto-imports, Vite transforms, rendering modes.
Pages
- The startup sequenceWhat actually happens between typing nuxt dev and getting a URL — c12 config loading, schema resolution, the hookable instance, module order, app resolution, the Vite and Nitro builds.
- Nitro and h3The server engine underneath Nuxt — presets and .output, route rules, cached handlers, storage, per-request state, server plugins, and how a module extends all of it.
- The unjs toolbeltThe unjs packages Nuxt is assembled from, what each one does for a module or layer author, and where you actually meet them while writing a toolkit.
- Auto-imports and how they biteHow unimport builds two separate registries and rewrites your identifiers at build time, why module runtime code must import from
- Vite, unplugin and build-time transformsThe Vite plugin hooks a module author uses, how addBuildPlugin and unplugin give one implementation for every builder, source-map-safe edits with magic-string, and dev-server hygiene.
- Rendering modes and dataUniversal, SPA, hybrid and static rendering; islands and lazy hydration; the real option list for useAsyncData and useFetch; the payload, plugins and unhead.
- Layers vs modulesThe decision rule in one sentence, why a company toolkit is almost always both, and where the deep treatment lives.
Notes for the whole section