Code Reference

Glossary

Next.js · Reference cheat sheet

Glossary

Next.js · Reference cheat sheet


📋 Overview

Alphabetical glossary of Next.js terms spanning App Router, rendering, caching, and deployment.

🔧 Core concepts

TermDefinition
App RouterRouting system based on the app/ directory and special files.
CSRClient-side rendering in the browser after JS loads.
Dynamic segmentFolder like [id] that captures a URL parameter.
Edge runtimeLightweight runtime for Middleware and some Route Handlers.
HydrationAttaching client React to server-rendered HTML.
ISRIncremental Static Regeneration — update static pages after deploy.
LayoutPersistent UI wrapper (layout.tsx) shared by child routes.
MiddlewareEdge code that runs before a request is completed.
Partial PrerenderingHybrid static shell + dynamic holes (version-dependent).
PrefetchLoading a route in the background via Link.
Route Handlerroute.ts exporting HTTP methods as an API endpoint.
Route group(name) folder that organizes routes without affecting the URL.
RSCReact Server Component rendered on the server by default.
Soft navigationClient transition without full document reload.
SSGStatic Site Generation at build time.
SSRServer-Side Rendering on each request.
StreamingSending UI in chunks via Suspense / loading.tsx.
TurbopackRust-based bundler used in modern next dev.

💡 Examples

Dynamic segment mental model:

app/shop/[slug]/page.tsx  →  /shop/shoes

RSC vs client:

// Server (default)
export default async function Page() { /* fetch, await */ }

// Client
"use client";
export function Widget() { /* useState, onClick */ }

⚠️ Pitfalls

  • Glossaries drift — verify behavior against your installed Next.js major version.
  • “Static” vs “dynamic” depends on APIs used (cookies, headers, no-store), not folder names alone.

On this page