nextjslisted

# Next.js Reference for Next.js 16+ App Router projects. Prefer the project's existing conventions, then steer with four leading words: **boundary**, **dynamic by default**, **pass-through**, and **generated types**. The adoption, optimization, and development-loop references target Next.js 16.3+. Check their prerequisites before using them on a 16.x project; an upgrade is a separate change, not an implicit part of a runtime check. Prefer installed-version docs in `node_modules/next/dist/docs/` (bundled since 16.2). Locate guides by filename because directory prefixes are numbered. For earlier versions, use the matching official upgrade or API documentation. Error pages under `/docs/messages/` must be read online. Branch-specific references, loaded on demand: - [boundary.md](boundary.md) — server/client split, providers, `server-only`, where state and files go. - [caching.md](caching.md) — `use cache`, `cacheLife`, `updateTag` vs `revalidateTag`, and the traps that pass `next build`. - [actions-and-routes.md](actions-and-routes.md) — Server Actions, Route Handlers, `proxy.ts`, metadata. - [typescript.md](typescript.md) — `PageProps`/`LayoutProps`/`RouteContext`, `typedRoutes`, `satisfies`, discriminated unions. - [view-transitions.md](view-transitions.md) — `<ViewTransition>`, canary-only. - [migration.md](migration.md) — what changed from 15, renames, removals. ## First Checks 1. Locate `next.config.{js,ts,mjs,cjs}` and use its directory as the project root.