Next.js is the React framework for building full-stack web applications by extending React features and integrating JavaScript tooling for faster builds. It is useful for projects that need server rendering and hybrid approaches, including static site generation and static outputs. Documentation and learning resources are available at nextjs.org, with community support via GitHub Discussions and Discord.
Project status
- Actively maintained: Yes. The source shows frequent updates in early July 2026, with the most recent upstream push matching today (2026-07-09).
- Update cadence: Fast and continuous, dominated by v16.3.0 canary updates (daily or near-daily across 2026-07-01 to 2026-07-08), plus at least one preview update in late June (2026-06-25).
AI summary generated
Recent updates
v16.3.0-canary.83
Release v16.3.0-canary.83 includes a fix to support LightningCSS draft `@custom-media` queries, plus documentation updates (including a new building guide and cache components migration guidance). It also adds an experimental TypeScript CLI backend to enable TypeScript 7 during production builds.
BreakingFeaturesv16.3.0-canary.82
v16.3.0-canary.82 adds new Turbopack/Next build behavior around compiling and serving service workers registered from the Pages Router, and updates agent-rules tooling to be verifiable and self-upgrading. It also bumps React to a newer experimental commit and includes CI and test-structure tweaks.
BreakingFeaturesv16.3.0-canary.81
This canary release includes a mix of developer-facing fixes and Turbopack behavior adjustments, plus several create-next-app template tweaks. A key internal rename is present for RSC HMR endpoints, and Turbopack changes include import behavior and cache eviction/persistence heuristics.
BreakingFeaturesv16.3.0-canary.80
v16.3.0-canary.80 is a canary release focused on Server Components HMR cancellation behavior, Turbopack-related runtime context, and edge adapter output configuration. It also includes a SWC and rust-react-compiler upgrade plus a variety of CI and test adjustments.
v16.3.0-canary.79
This canary release includes multiple internal “misc” changes across Turbopack, CI stats reporting, development behavior for Server Components HMR, and runtime instrumentation. It also upgrades the embedded React/ReactDOM experimental build and adjusts template handling to rewrite `require` imports during app-router page expansion.
Featuresv16.3.0-canary.78
v16.3.0-canary.78 adds a new experimental flag, serverComponentsHmrCancellation, intended to cancel in-flight render and validation work when a newer Server Component HMR refresh supersedes it (development only). The code also wires this option through config typing, build-time env defines, and the app render handler templates.
Featuresv16.3.0-canary.77
v16.3.0-canary.77 is a mixed “misc changes” release focused on internal browser bundling correctness, dev-only behavior, cacheLife typing, and font data updates. It also refreshes an example to use React 19.2.10+ SubmitEvent instead of FormEvent.
Featuresv16.3.0-canary.76
v16.3.0-canary.76 is a build and client navigation-focused canary that tweaks Instant Navigation Testing behavior under the instant navigation lock, improves cache and refresh handling, and reorders prefetch scheduling for better prioritization. It also upgrades React to a newer experimental commit and includes several CI and build-related adjustments.
v16.3.0-canary.75
v16.3.0-canary.75 is presented as a set of misc changes focused on Instant Navigation testing improvements, CI/test workflow tweaks, and Turbopack validation compatibility. The release notes do not mention build tooling or internal developer workflow changes, but the diff shows additional non-noted modifications.
Featuresv15.5.20
The release notes for v15.5.20 claim the only change was publishing `@next/swc-wasm-web` that was accidentally not published since 15.5.15. However, the provided code diff shows a much broader set of changes across core Rust crates (`next-core`, `next-api`, and `napi`) plus CI/workflow changes. Several of these code changes include behavior and API signature changes that are not mentioned in the release notes.
v16.2.10
Release v16.2.10 release notes only claim that publishing for `@next/swc-wasm-web` was fixed (it was accidentally not published since 16.2.4). The provided code diff, however, shows substantial additions to repository-local agent/authoring documentation under `.agents/skills/**`, including multiple new skills and documentation tooling references. No consumer-facing code, exported API surface, or `@next/swc-wasm-web` implementation changes are evident in the diff excerpts shown.
v16.3.0-preview.5
v16.3.0-preview.5 includes Turbopack work to discover and compile client-registered service workers, plus several smaller runtime and dev workflow tweaks. The most concrete code change in the provided diff is new service worker compilation wiring in next-api, backed by new service worker chunking context support in next-core.
Featuresv16.3.0-preview.4
This preview release changes CI behavior related to native bindings, making automatic native binding installation opt-in instead of happening by default. If your workflow previously relied on automatic binding installs, you may need to adjust your CI or configuration to enable the new behavior.
Breakingv16.3.0-canary.67
Next.js v16.3.0-canary.67 updates Instant Navigation Testing behavior and dev-time validation around Cache Components and `instant = false`, and includes an ImageResponse-related fix for local fonts in statically prerendered metadata routes. It also adds internal logic to suppress a `prefetch={true}` warning when routes opt out via `instant = false`, plus documentation and test coverage changes.
Breakingv16.3.0-canary.66
v16.3.0-canary.66 is a canary focused on partial prefetching and PPR-related internal wiring. The release notes call out a revert of legacy PPR codepaths, improved dev overlay/insights for Link prefetch partial errors, and some navigation inspector and test/CI workflow tweaks.
Featuresv16.3.0-canary.65
This canary release focuses on Next.js developer-experience fixes around cache components and request header handling. It also adjusts dev-only caching behavior for `cacheMaxMemorySize: 0` and improves safety when stripping internal headers.
v16.3.0-canary.64
This canary release adds Turbopack changes for chunking behavior, including support for single-entry (single-chunk) output that inlines the full module closure into one file. It also introduces a debug dump toggle for CSS chunking via TURBOPACK_DEBUG_CSS_CHUNKING and adjusts chunk merging behavior for CSS based on overlap. Finally, CI publishing is updated to publish based on release tags instead of branch pushes.
Featuresv16.3.0-canary.63
v16.3.0-canary.63 focuses on instant navigation and prefetch behavior around ISR fallbacks, plus assorted devtools and dev overlay UI/insights cleanups. The code introduces a mechanism to flag upgradeable ISR fallback shells for per-segment prefetches and retries them until concrete params are available, alongside an update to how the instant nav lock cookie is released.
Featuresv16.3.0-canary.62
v16.3.0-canary.62 is a small canary focused on Turbopack-related build behavior adjustments, plus documentation improvements (Interactive Apps guide) and some internal housekeeping for agent “skills”. It also includes a fix related to `export const dynamic` detection when `nextConfig.cacheComponents` is enabled.
Featuresv16.3.0-canary.61
v16.3.0-canary.61 is a canary release focused on Cache Components adoption tooling (including a new codemod opt-out), plus several targeted fixes and documentation updates. It also updates React to a newer canary build and includes some Turbopack and runtime-related changes mentioned in the release notes.
Features