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: The upstream push and updates are happening today (latest upstream push at 2026-09-10), with a steady stream of canary artifacts over the past few days, indicating ongoing active development rather than maintenance mode.
- Apparent cadence: Multiple canary updates landed within about a week (examples: 2026-09-03 through 2026-09-09), suggesting a high-frequency canary cycle with frequent CI/test and Turbopack-related refinements.
AI summary generated
Recent updates
v16.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.
Breakingv16.4.0-canary.16
v16.4.0-canary.16 is a canary release with mixed items including Turbopack tracing performance work, improved behavior for unrecognized Server Actions, and client-side Web Vitals reporting changes. It also upgrades the embedded React/ReactDOM canary build and introduces a new GitHub workflow/script to auto-close verified “Next Maintainer” issues on an hourly schedule.
BreakingFeaturesv16.4.0-canary.15
v16.4.0-canary.15 contains a set of Turbopack and build-system changes, including reducing Turbopack cache usage and removing the worker thread used for Turbopack builds. It also bumps SWC to v77 and upgrades the bundled React (and ReactDOM) build to a new experimental commit.
v16.4.0-canary.14
This canary release includes multiple cache-related and workflow documentation updates, along with turbopack memory accounting improvements. The most substantive code changes are in turbopack, where memory reporting is adjusted to reflect mimalloc behavior and cache wrapper logic drops Edge runtime specific handling.
v16.4.0-canary.13
v16.4.0-canary.13 is a misc-focused canary release with internal CI and test updates, plus runtime and dev-experience tweaks like lazy server HMR and a Turbopack HMR recovery fix. The release notes also mention a React upgrade and several docs changes around caching and layout stability.
v16.3.4
v16.3.4 is described as a backport-style patch release that re-enables AVIF Image Optimization and includes a small set of bug fixes. The release notes specifically call out fixes for testmode infinite recursion, a TypeScript alias build error, and an unset crossOrigin in Turbopack manifests.
v15.5.25
Release v15.5.25 is described as a follow-up that re-enables AVIF Image Optimization when newer versions of `sharp` are installed. The provided code diff, however, shows multiple unrelated runtime and build-time behavioral changes across Next.js routing, metadata image handling, and CSS import validation that are not mentioned in the release notes.
v16.4.0-canary.12
This canary release mainly contains miscellaneous maintenance: it removes the scheduled "popular" workflow and its Slack notifier action, and adjusts codemod behavior for non-interactive upgrades and .mjs transformation. In turbopack, it also changes how SST key blocks omit per-entry hashes, ensuring keys are stored in key order when hashes are not present.
v16.4.0-canary.11
This canary release bundles a set of Turbopack fixes and build/runtime correctness changes, including routing and cache-key improvements plus image-optimizer refactors. It also introduces new internal configuration plumbing for Turbopack, including React experimental channel selection and export name mangling behavior.
Featuresv16.4.0-canary.10
v16.4.0-canary.10 adds a new create-next-app option for Cache Components, and expands Next.js routing internals around parallel routes and route matching (including stricter matcher pruning behavior behind new config plumbing). It also updates server action routing/action-manifest handling for app routes and bumps several dependencies (notably React canary and Turbopack-related Rust deps).
BreakingFeaturesv16.4.0-canary.9
v16.4.0-canary.9 contains multiple small fixes and experimental wiring changes, including updates to ReactDOM bailout handling behind a flag, image pipeline tweaks, and React and Rust toolchain upgrades. It also includes several Turbopack and Rust-side changes that affect build-time behavior and compilation patterns.
Featuresv16.4.0-canary.8
v16.4.0-canary.8 is a canary release focused on evaluation harness updates (including new evals for detecting whether an agent truly uses Next.js) and Turbopack/monorepo-related resolution fixes. It also updates the create-next-app default favicon and changes the CI workflow used to upload preview tarballs to Vercel packages using short-lived, OIDC-based authorization. A dependency bump to @vercel/agent-eval 2.2.1 is included.
SecurityFeatures