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
- Next.js (vercel/next.js) appears actively maintained, with upstream pushes and frequent updates in early/mid September 2026, including a new canary the same day as the last upstream push (2026-09-17).
- The apparent update cadence is high and consistent for a canary channel, with multiple consecutive
v16.4.0-canary.*updates roughly every 1 to 2 days across 2026-09-09 to 2026-09-16.
AI summary generated
Recent updates
v16.4.0-canary.35
v16.4.0-canary.35 is a release focused on agent workflow improvements and multiple Next.js internal infrastructure updates. Notable items include Turbopack GC configuration support, switching compression from lzzzz to lz4_flex, and bumping SWC to 79.x, along with several agent and documentation refinements.
Featuresv16.4.0-canary.34
v16.4.0-canary.34 includes several internal router and caching changes, plus Turbopack and compiler-side adjustments. Key documented items include switching internal join behavior (where appropriate), preserving committed App Router fallback response status, and adjusting server actions transform output to ensure directives remain first.
BreakingFeaturesv16.4.0-canary.33
v16.4.0-canary.33 includes a locale path matching fix for the App Router when used with Pages i18n, and it upgrades the bundled React dependency to a newer experimental revision. The code diff provided, however, shows additional ReactDOM behavioral changes beyond the release notes, mostly inside the compiled ReactDOM event system and DOM position validation logic.
BreakingFeaturesv16.4.0-canary.32
v16.4.0-canary.32 is a canary release focused on routing and deployment correctness, with additional Turbopack tracing and test coverage improvements. The most visible functional themes in the notes are Pages Router prefetch marker handling, adapter deployment query correctness, and caching behavior around (never-)prerenderable fallback params.
v16.4.0-canary.31
v16.4.0-canary.31 updates Next.js/Turbopack behavior around convention-based file detection, most notably fixing how proxy.ts is detected when `pageExtensions` is compound (for example, `proxy.page.ts`). It also adjusts Turbopack-related build/runtime internals (proxy/middleware detection in Rust and convention parsing in TS), and adds an option to wait for Turbopack shutdown during `next dev` sessions.
Featuresv16.4.0-canary.30
v16.4.0-canary.30 includes dev tooling changes (HMR exposure of App Router runtime errors, codemod marker and upgrade behavior updates) plus some chunking/performance optimizations. It also updates the vendored @mswjs/interceptors version and refreshes Next codemod documentation and fixtures.
Featuresv16.4.0-canary.29
This canary release contains three main changes: a fix for durable `use cache` behavior when runtime environment variables are mutated, a refactor in Turbopack around `new_atom` string handling, and some test serialization for Turbo Tasks trybuild tests. The code diff shows that the `use-cache` implementation was adjusted to change how runtime env var state contributes to cache keys across rendering phases.
v16.4.0-canary.28
This canary release makes Turbopack's TypeScript result handling more explicit by separating the actual payload from shared metadata (issues). It also updates OpenTelemetry E2E tests to better stabilize the collector lifecycle across the test suite.
Breakingv16.4.0-canary.27
v16.4.0-canary.27 includes a set of miscellaneous Next.js changes and CI/devtool fixes. Documented highlights include cache and staging validation tweaks, a React upgrade, an experimental next/image config, and Turbopack behavior improvements in development.
Featuresv16.3.5
v16.3.5 is a backport-focused release, primarily addressing correctness bugs across Next.js subsystems, including next/image disk caching, server NFT generation behavior, CSP nonce handling, and prerender signal retention. The release notes list several targeted fixes, but the provided code diff shows additional build graph and manifest-related changes that are not mentioned.
v16.4.0-canary.26
v16.4.0-canary.26 is a mixed canary release spanning core runtime, Turbopack behavior, developer tooling (bundle-analyzer), and CI/scripts cleanup. Notable documented items include routing canonicalization and improved route erroring, plus bug fixes for next/image socket reuse and duplicate background revalidation.
BreakingFeaturesv16.4.0-canary.25
v16.4.0-canary.25 adds historical snapshot support to the bundle-analyzer and includes a set of Cache Components and prefetching-related updates across core, docs, and tests. The release notes also mention improvements to relative-path handling and webpack loader behavior.
Featuresv16.4.0-canary.24
This canary release includes a set of internal CI and test changes plus two Next.js runtime behavior fixes related to Turbopack HMR and bundler config validation skipping in test-like phases. It also removes the `tsec` tool and updates typecheck scripts accordingly, and re-enables publishing for `@vercel/devlow-bench.
Featuresv16.4.0-canary.23
v16.4.0-canary.23 contains a mix of Turbopack fixes, build/test stabilization, and several Next.js documentation and example updates. It also upgrades the bundled React experimental version and expands WebAssembly support for the next-napi-bindings toolchain. Overall, the release notes describe the changes at a high level, but the code diff shows at least one significant internal protocol/schema change that is not mentioned.
Featuresv16.4.0-canary.22
v16.4.0-canary.22 includes documented loader API changes, specifically adding support for `.resolve`, plus updates to developer workflow docs around preserving Next.js development state. The diff also shows internal changes to the eval harness to support optional fixture-specific runtime setup.
Featuresv16.4.0-canary.21
v16.4.0-canary.21 contains mostly internal changes, including a SWC version bump, multiple turbo-tasks and cache rendering tweaks, and CI/workflow adjustments. The release notes emphasize PPF and dev validation behavior for caches, plus several testing and build stability fixes.
v16.4.0-canary.20
v16.4.0-canary.20 includes a targeted fix for turbopack’s turbo-tasks backend where strongly consistent reads could hang when the relevant task was canceled. It also includes test and Turbopack-related misc cleanups, plus a Next.js hot reloader adjustment intended to stabilize successive HMR test behavior.
v16.4.0-canary.19
v16.4.0-canary.19 includes a small fix in the Next.js dev overlay, specifically addressing route info segment override updates not propagating correctly in development. The code changes also introduce a more fundamental change to how the dev overlay’s segment trie updates internal node snapshots to support immutable state for React store consumers.
v16.4.0-canary.18
Next.js v16.4.0-canary.18 includes targeted fixes around prerender/runtime tracking and Turbopack CSS source map correctness. It also adds API reference documentation for the advanced Proxy flags skipProxyUrlNormalize and skipTrailingSlashRedirect. Code changes indicate additional behavior adjustments around how params/searchParams are treated as “hanging” inputs during final runtime prerenders, plus an update to the “unexpected cache miss” warning implementation.
v16.4.0-canary.17
This canary release changes the default for the experimental adapter route collapsing behavior, enabling it by default. It also updates the `next info` CLI implementation and tests to avoid leaking “missing package manager” command errors.
Breaking