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: Upstream activity is current (last upstream push matches today, 2026-07-30), and the feed shows frequent recent updates (preview and canary builds), indicating ongoing development rather than maintenance mode.
- Cadence: Multiple updates landed within about a week (e.g., v16.3.0-canary.95 through .102 from 2026-07-23 to 2026-07-28, plus a v16.2.12 and v15.5.22 on 2026-07-25), suggesting a fast-moving release train for Next 16.3.x.
AI summary generated
Recent updates
v16.3.1-canary.2
v16.3.1-canary.2 is a miscellaneous canary release focused on Turbopack fixes and test coverage, plus a React experimental upgrade. It also adjusts prerender bypass matching for HTML-limited bots and makes several documentation and CI permission tweaks.
v16.3.1-canary.1
v16.3.1-canary.1 includes changes to Turbopack runtime-chunk handling, stream scheduling for “waitForAllReady”, and App Router behavior around per-segment prefetching. The release notes describe documentation updates and several Turbopack fixes, plus a rename of the static-generation stream option.
Breakingv16.3.1-canary.0
This canary release primarily fixes a segment cache keying bug where an optional catch-all route's index content could be served for other slug values. The fix updates internal segment-cache logic around how entries are keyed using server-reported vary parameters, and it adds an e2e regression test to prevent reintroductions.
v16.3.0
v16.3.0 includes a large set of framework, Turbopack, and App Router related fixes, including security-related dependency updates and multiple prefetch, HMR, and caching improvements. The code diff also reveals a few behavior changes that are not clearly described in the provided release notes, most notably around TypeScript CLI defaults and how “instant” interacts with Partial Prefetching.
SecurityFeaturesv16.3.0-canary.107
This canary release updates Next.js Turbopack behavior so the Turbopack filesystem cache for builds is enabled by default. The change updates both the runtime default configuration and the related documentation and e2e test expectations.
Breakingv16.3.0-canary.106
This canary primarily updates Next.js App Router cache component behavior related to the deprecated experimental.useCache option. It also adds logic to ensure hybrid Pages and App Router 404 handling works correctly by setting request metadata needed to render the App Router not-found output.
Breakingv16.3.0-canary.105
This canary release focuses on Turbopack chunking configuration and several App Router build/runtime fixes. It also introduces an automated code review workflow and upgrades the bundled experimental React/ReactDOM builds.
Featuresv16.3.0-canary.104
v16.3.0-canary.104 is a canary release focused on Next.js rendering and metadata streaming behavior, specifically around htmlLimitedBots and PPR shell handling. It also removes the obsolete shouldWaitOnAllReady render option, updates create-next-app messaging, and includes React version bumps that bring additional runtime behavior changes.
Breakingv16.3.0-canary.103
This canary release is primarily a collection of misc changes, including several documentation updates (notably around offline support and adapter docs), and targeted fixes/behavior tweaks in the rendering and navigation subsystems. On the implementation side, it introduces new infrastructure for HMR version aggregation between browser and node, plus additional runtime wiring for App-router-related server-side HMR chunk lists.
Featuresv16.3.0-canary.102
v16.3.0-canary.102 is a canary release focused on Turbopack tree-shaking and dynamic import behavior, plus documentation for the experimental offline support feature. Turbopack changes include re-export tracking adjustments and logic to avoid loading dropped dynamic import targets, alongside a new and expanded `experimental.useOffline` guide.
v16.3.0-canary.101
This canary release focuses on Turbopack server HMR behavior, including changes to how build events are reported and how server HMR reacts to graph changes. The code diff reveals a significant internal refactor that aggregates server-side HMR updates into a single subscription, with corresponding changes to update instruction types and server fast refresh signaling.
Featuresv16.3.0-canary.100
v16.3.0-canary.100 bundles several Turbopack, tracing/Instant Insights, and CI/CD related changes, along with React canary and doc updates. The code diff shown includes new import.meta.env handling that derives a base URL from Next config, plus changes to production tracing globs and trace-related glob option defaults.
Featuresv16.3.0-preview.10
v16.3.0-preview.10 is a large internal update focused on prefetching behavior changes, especially around Partial Prefetching versus the older allow-runtime model, plus multiple scheduler, caching, and dev tooling adjustments. The release also updates React and several vendored dependencies, and includes a variety of Turbopack and sourcemap related performance tweaks.
BreakingFeaturesv16.3.0-canary.99
This canary release (v16.3.0-canary.99) has no meaningful release notes content beyond the text 'Initial release'. The code diff shows multiple internal Next.js runtime changes spanning proxying, request insight CLI output, caching and prefetch scheduling logic, build trace configuration, and embedded React DOM experimental bundle behavior.
v16.3.0-canary.97
Release v16.3.0-canary.97 focuses on developer-experience improvements around dev validation, source map handling, and sandbox reliability, plus internal refactors and benchmarks for those workflows. The release notes also mention a new `experimental.devValidationWorker` config flag and several sourcemap and HMR-related fixes.
Featuresv16.2.12
Next.js v16.2.12 release notes describe only backported documentation fixes and a backport intended to support TypeScript 7. No user-facing API changes, behavioral changes, or breaking changes are explicitly called out in the release notes.
v15.5.22
v15.5.22 release, with release notes stating that Next.js now rejects TypeScript versions >= 7 using an actionable error. The provided code diff shows many additional changes across Next core, Next API, and CI/build scripts that are not mentioned in the release notes.
Breakingv16.3.0-canary.96
Next.js v16.3.0-canary.96 includes a set of internal “misc changes” focused on prerendering metadata, routing/rendering performance, and improved developer diagnostics (for example, source map behavior and 404 handling). The diff also shows several stricter build-time validations and runtime template refactors that are not fully described in the release notes.
Featuresv16.3.0-canary.95
Next.js v16.3.0-canary.95 focuses on internal Turbopack watcher refactors, React version upgrade, and stricter runtime/build-time validation around generateStaticParams for output: export. It also adjusts Google Fonts fetch behavior (bounded timeouts), rewrites edge server source map handling, and includes benchmark harness improvements.
BreakingFeaturesv16.3.0-preview.9
v16.3.0-preview.9 contains a set of internal Turbopack, SWC transform, and App Router caching/HMR changes. Several performance-oriented plumbing updates and React experimental build bumps are included alongside partial prefetching adoption refinements and new static-params HMR behavior.
BreakingFeatures