Conrad Nuxt docs

Train

Conrad Nuxt docs

Nuxt questions for the Conrad interview, written from your four Nuxt docs notes — rendering modes and route rules, the request lifecycle and islands, routing, data fetching, state and errors, the Nitro server and response fragmentation, performance, assets and testing.
Nuxt lifecycleData fetchingServer

Written from your Nuxt docs notes: Getting started I, Getting started II, Getting started III and Concepts. The questions are general ones, the way an interviewer asks them: how the thing works, when you'd use it and what goes wrong, not the wording of your notes. They sit next to Conrad Nuxt, which covers hydration, config, memory leaks, modules and layers; the docs facts themselves are drilled in Nuxt docs, chapter by chapter.

Know

PageCoversQuestions
Rendering and lifecycleCSR, SSR and SSG, swr versus isr, prerendered data, live data on a prerendered page, CORS and the proxy rule, what runs in which order, server components and nuxt-client9
Routing, data and stateWhat a <NuxtLink> click does, route versus server middleware, an auth middleware, $fetch versus useFetch versus useAsyncData, keys, await versus lazy versus server: false, cookies during SSR, useState limits, errors, SEO tags12
The Nitro serverh3, unstorage and unenv, server routes and their types, validation, event.$fetch, middleware versus plugins and hooks, response fragmentation, the three ways to cache, varies, an authenticated handler util11
Performance, assets and testingWhere to start on a slow page, lazy components versus lazy hydration, prefetching, Nuxt Image, Fonts and Scripts, assets versus public, static files in Kubernetes and on Workers, fonts and CLS, LCP, the test environments11
  • Drill them: Train, press Only next to Conrad Nuxt docs, Smart order. Every multiple-choice answer is spread across A to D, so the letter tells you nothing.
  • Rehearse: a mock interview with the Conrad sections selected.

Be able to say

Be able to say· How do you choose a rendering mode for each part of a Nuxt app?

"I start from what the page needs. Content that changes only with a deploy, like legal or help pages, I prerender: it's the cheapest to serve, but the data is baked in at build time. Public pages that change during the day, like categories and product pages, I render on the server and cache with swr, so most users get a cached copy and it refreshes in the background. Pages behind a login with no SEO value, like an account area or an admin, can be ssr: false. And when one part of a cached or prerendered page has to be live, like stock, I fetch just that part in the browser with server: false."

Pages in this section

  1. 01Rendering and lifecycleCSR, SSR and prerendering, route rules (swr, isr, prerender, ssr false, cors, proxy), data baked into prerendered pages, CORS, the order things run on the server and in the browser, and server components with nuxt-client and slots.
  2. 02Routing, data and stateWhat happens on a NuxtLink click, route middleware versus server middleware, $fetch versus useFetch versus useAsyncData, keys, await versus lazy versus server false, cookies during SSR, what useState is and isn't, errors on the server and in the browser, and SEO tags.
  3. 03The Nitro serverh3, unstorage and unenv, server routes and their types, validated input, event.$fetch, server middleware versus Nitro plugins and their hooks, response fragmentation with render:html and render:response, the three ways to cache, varies, and a reusable authenticated handler.
  4. 04Performance, assets and testingWhere to start on a slow page, lazy components versus lazy hydration, NuxtLink prefetching, Nuxt Image, Fonts and Scripts, app/assets versus public, serving .output/public in Kubernetes and on Workers, fonts and layout shift, LCP, and Nuxt's test environments.

Your notes

Open in Notes

Nothing yet. Notes filed here show up on every page of this section.

Layers vs modules

The decision rule in one sentence, why a company toolkit is almost always both, and where the deep treatment lives.

Rendering and lifecycle

CSR, SSR and prerendering, route rules (swr, isr, prerender, ssr false, cors, proxy), data baked into prerendered pages, CORS, the order things run on the server and in the browser, and server components with nuxt-client and slots.