SYSTEM Cited by 2 sources

Next.js

Next.js is a Vercel-backed React application framework providing server-side rendering, file-system-based routing, app router, API routes, image optimization, and caching / revalidation primitives. Historically opinionated toward Vercel as the deployment target; systems/opennext fills the gap for other runtimes.

Stub

This page only covers Next.js capabilities named by currently- ingested sources. Broader Next.js architecture (App Router, Pages Router, ISR, RSC internals) is out of scope until a source describes them.

Relevant primitives (named by ingested sources)

• force-dynamic (Next.js caching guide) opts a route out of static rendering. In the 2025-10-14 Cloudflare post, dynamic vs non-dynamic mode interacted with OpenNext's streaming behaviour: non-dynamic rendering buffers the full response before sending any bytes; dynamic mode streams.
• Rendering pipeline uses pipeThrough() chains that (per Cloudflare profiling) allocate up to 50 × 2048-byte Buffer instances per request even when most aren't used.
• Caching / deduplication — when multiple concurrent requests hit the same page, Next.js (via OpenNext's composable cache) deduplicates rendering to a single invocation.
• JSON.parse(text, reviver) — used heavily internally; 100,000+ reviver invocations observed per request on the Cloudflare benchmark; hot enough that Cloudflare's V8 patch speeding up parse-with-reviver is a noticeable win.

Seen in

• sources/2025-10-14-cloudflare-unpacking-cloudflare-workers-cpu-performance-benchmarks — Cloudflare's profiling of cf-vs-vercel-bench surfaced Next.js internals (rendering pipeline, reviver usage, force-dynamic behaviour) as meaningful contributors to the apparent Vercel-vs-Workers gap.
• sources/2026-02-24-cloudflare-how-we-rebuilt-nextjs-with-ai-in-one-week — Cloudflare reimplements the Next.js API surface from scratch on Vite as vinext in ~1 week / ~$1,100 in Claude tokens, hitting 94 % API coverage with 1,700+ Vitest + 380 Playwright tests ported from the Next.js repo. Canonical wiki instance of Next.js as a "well-specified target API" — extensively documented, massive user base, heavily represented in training data, comprehensive test suite portable as executable spec. Builds against 16.1.6 + Turbopack in the 7.38 s baseline benchmark; vinext comes in at 4.64 s (Rollup) and 1.67 s (Rolldown). Also surfaces the build-time-scales-linearly-with-generateStaticParams() pathology that vinext's Traffic-aware Pre-Rendering addresses by querying zone analytics at deploy time.

Related

• systems/opennext — OSS adapter enabling Next.js on non- Vercel runtimes (systems/cloudflare-workers, AWS Lambda, Netlify).
• systems/vinext — Cloudflare's clean reimplementation of the Next.js API surface on Vite, structurally distinct from the adapter approach.
• systems/turbopack — Next.js's in-house Rust bundler.
• systems/vite — the ecosystem-alternative build tool powering most non-Next frameworks and vinext.
• systems/react — the UI framework Next.js is built on.
• systems/cloudflare-workers — a Next.js deployment target via OpenNext, now also natively via vinext.
• patterns/clean-reimplementation-over-adapter — the structural alternative to OpenNext's adapter approach.
• concepts/traffic-aware-prerendering — the deploy-time generateStaticParams() alternative vinext introduces.