Written from your Nuxt note for the interview on 14 October 2026. The questions sit in the middle: how things work and why you'd choose them, not API trivia and not one-line overviews. The deeper material stays in the other sections, such as Hydration errors, Under the hood and Module authoring.
| Page | Covers | Questions |
|---|---|---|
| Rendering and hydration | From request to interactive page, the payload, $fetch versus useFetch, hydration mismatches, SSR trade-offs and per-route rendering, Nitro and its presets, tree-shaking | 6 |
| Config, state and memory | runtimeConfig versus app.config versus generated templates, where secrets go, cross-request state, memory leaks | 4 |
| Modules, plugins and layers | Module versus plugin, what a module can do, the three kinds of hooks, an observability module, layers and their priority, layer or module | 8 |
"The server creates a fresh Nuxt app for the request and renders it to HTML, waiting for useFetch and useAsyncData, and puts their results, the shared state and the public config into a payload inside the HTML. The browser shows the HTML immediately, downloads the JavaScript, and Vue hydrates: it builds the same tree, reuses the existing DOM, attaches the listeners and takes the data from the payload instead of fetching it again. From then on it's a single-page app."
Nothing yet. Notes filed here show up on every page of this section.
Load testing
Load testing a storefront with k6 — smoke, load, stress, spike and soak tests, realistic journeys and URL mixes, thresholds, and what to watch while the test runs.
Rendering and hydration
What happens from a request to an interactive Nuxt page, what the payload carries, why plain $fetch in setup causes double requests, hydration mismatches and how to find them, SSR trade-offs with per-route rendering, and tree-shaking.