All quizzesHard
Edge & Streaming
Preview — 3 of 10 questions
How do you use Nitro plugin hooks to intercept and modify server-rendered HTML responses?
AUse afterEach hook in nuxt.config.ts — it runs after every SSR render
BOverride the _render.ts file in .nuxt/ directory with custom HTML processing
CUse defineNitroPlugin with the render:html hook to intercept and mutate the HTML output before it is sent to the client
DUse a Nuxt plugin with mode: 'server' and return a transformed HTML string
What are the specific constraints when deploying a Nuxt app to edge runtimes (Cloudflare Workers, Vercel Edge)?
AEdge runtimes support all Node.js APIs — they are identical to Node.js servers
BEdge functions cannot access environment variables — use client-side storage instead
CEdge runtimes only support static file serving — no server-side logic is possible
DEdge runtimes run V8 isolates — they lack Node.js built-ins (no fs, net, child_process), have limited CPU time, constrained memory, and require all code to be bundled into a single script
What is streaming SSR and how does it improve perceived performance?
AStreaming SSR splits the JavaScript bundle into chunks that download in parallel
BStreaming compresses the SSR HTML using gzip before transmission
CStreaming SSR sends HTML to the browser progressively as Vue renders each component tree segment — allowing browsers to start rendering and fetching critical resources before the full HTML is ready
DStreaming SSR is the same as ISR — both involve incremental page generation
Sign up free to play
Answer all 10 questions (7 more), see explanations for every answer, and track your score.