BasicNext.js Orientation and the App Router Bet45 minLesson 4 of 8
Trace what happens between next dev, next build, and an incoming production request.
The illustrated walkthrough is behind sign-in.
Every prompt in the library is public. Any free InterviewOS account unlocks the diagram, the model answer, and the self-check.
Start with the answer
Overview
Sign in to read the model answer. Sign in
Objectives
What you'll learn
- Describe what next dev, next build and next start each actually do.
- Trace a production request from the edge to rendered HTML.
- Explain why a bug that only appears after next build is usually a rendering-mode bug.
Terms to know
Glossary
- Turbopack
- The bundler behind next dev and next build. It compiles routes on demand in development, which is why the first visit to a route is slower than later ones.
- Build output summary
- The per-route table next build prints, stating whether each route is static, dynamic or partially prerendered. The authoritative answer to "what did it decide?"
- Streaming
- Flushing the HTML shell before all data resolves, then sending suspended subtrees as they finish.