building/route-table

7 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Build output route table symbols and meanings

Next.js prints a route table after a successful build with symbols indicating how each route is served: ○ (Static) is fully prerendered at build time and served without server rendering. ◐ (Partial Prerender) serves a static shell immediately with dynamic content streaming in at request time. ● (SSG) is prerendered static HTML from generateStaticParams or getStaticProps. ƒ (Dynamic) is server-rendered on demand for each request.

Revalidate and Expire columns in build output

Routes that contain cached functions or components show Revalidate and Expire columns in the build output. A route reports the shortest revalidate and expire values across all caches it contains. This applies even without an explicit cacheLife call, since caches use the default profile. Routes revalidate after the shortest revalidate value, and the Expire column caps at one year, shown as 1y.

Route table truncation with [+N more paths]

When there are more prerendered paths than fit in the table, Next.js prints a short list ending with [+N more paths] to indicate additional routes not shown.

Do not call Route Handlers from Server Components

Route Handlers should be used to access backend resources from Client Components, but should not be called from Server Components to avoid an additional server request.

Enhanced routing with layout deduplication and incremental prefetching in Next.js 16

Next.js 16 includes a complete overhaul of the routing and navigation system. Layout deduplication ensures when prefetching multiple URLs with a shared layout, the layout is downloaded once. Incremental prefetching means Next.js only prefetches parts not already in cache rather than entire pages. These changes require no code modifications and are designed to improve performance, though you may see more individual prefetch requests with lower total transfer sizes.

middleware renamed to proxy with nodejs runtime in Next.js 16

The middleware filename is deprecated and renamed to proxy to clarify network boundary and routing focus. The edge runtime is NOT supported in proxy; the proxy runtime is nodejs and cannot be configured. If you want to continue using the edge runtime, keep using middleware. Rename middleware.ts to proxy.ts and change the named export 'middleware' function to 'proxy'. Configuration flags containing 'middleware' are also renamed, for example 'skipMiddlewareUrlNormalize' is now 'skipProxyUrlNormalize'.

Parallel routes require explicit default.js files in Next.js 16

All parallel route slots now require explicit default.js files in Next.js 16. Builds will fail without them. To maintain previous behavior, create a default.js file that calls notFound() or returns null. Example: export default function Default() { notFound() } or export default function Default() { return null }

Give your agent this brain