All quizzesHard
App Router — Series 2
Preview — 3 of 10 questions
Which limitation is specific to code running in the Edge runtime (export const runtime = 'edge')?
ANo access to Node.js built-in modules (fs, net, child_process) or most native Node APIs — only Web-standard APIs (fetch, Request/Response, crypto.subtle) are available
BNo support for async/await
CEnvironment variables cannot be read
DIt cannot be used with TypeScript
What is instrumentation.ts at the project root for?
APlaywright E2E test configuration
BRegistering custom Webpack loaders
CRunning setup code once at server startup — typically to initialise OpenTelemetry, Sentry, or another monitoring tool — via an exported register() function
DDeclaring TypeScript path aliases
What does output: 'standalone' in next.config.ts produce, and why use it?
AA minimal, self-contained build in .next/standalone/ — a small server.js plus only the traced dependencies actually used — so a Docker image does not need the full node_modules/
BA single static HTML file with everything inlined
CIt disables server-side rendering entirely
DIt merges all API routes into one function
Sign up free to play
Answer all 10 questions (7 more), see explanations for every answer, and track your score.