{"id":650,"slug":"nextjs-16-cache-components-october-2025","title":"Next.js 16 (October 2025) made Partial Prerendering production via \"Cache Components\" with dynamic-by-default semantics","kind":"reference","scope":"business","status":"current","audiences":["claude-code","candid-team"],"topics":["tech-stack","framework-choice","build-tooling"],"reference_body":"**Claim:** Next.js 16 (released October 2025) shipped:\n\n- **Cache Components / PPR** is now the default story: everything is dynamic by default, caching is opt-in via the `\"use cache\"` directive with `cacheLife` / `cacheTag`.\n- **Turbopack** is the default dev bundler (production builds still in beta).\n- **middleware.ts** renamed to **proxy.ts**.\n- **React Compiler 1.0** stable opt-in (not enabled by default).\n\n**Source:** nextjs.org/blog/next-16.\n\n**Confidence:** Verified.\n\n**Migration implication:** Migrating from 14/15 to 16 requires a deliberate audit, not an `npm upgrade`. RSC footguns (client/server boundary placement, cookie handling on server fetches, waterfall fetches inside Server Components) all persist.\n\n**For Candid:** Next.js 16 is not the default for marketing sites. Cache Components solves problems most SMB sites don't have, and \"everything dynamic by default\" adds cognitive load for brochure work. See [[rule-prefer-astro-cloudflare-default-marketing-site]].","rationale_body":null,"metadata":null,"links":{"outgoing":[{"slug":"rule-prefer-astro-cloudflare-default-marketing-site","title":"RULE: Default stack for new marketing-site work is Astro 5/6 + Tailwind v4 on Cloudflare Pages","kind":"rule","scope":"business","link_type":"relates-to"},{"slug":"react-compiler-1-0-stable-oct-2025","title":"React Compiler 1.0 went stable October 7, 2025; battle-tested on Meta apps and fully production-ready","kind":"reference","scope":"business","link_type":"relates-to"}],"incoming":[]},"created_at":"2026-05-22T21:24:18.291Z","updated_at":"2026-05-22T21:24:18.291Z"}