Next.js
Frontend & MobileThe React Framework
Release History
v16.3.0-canary.87v16.3.0-canary.86v16.3.0-canary.85v16.3.0-preview.6v16.3.0-canary.84v16.3.0-canary.83v16.3.0-canary.82v16.3.0-canary.814 fixes2 featuresThis release includes several improvements to Turbopack, including enabling type imports by default and memory optimization. It also addresses various fixes in create-next-app and improves prefetching insights.
v16.3.0-canary.803 fixes1 featureThis release includes various miscellaneous improvements, notably running instrumentation for Node.js Middleware without an adapter and several test and CI stability fixes. Key updates include upgrading to swc 72 and rust-react-compiler.
v16.3.0-canary.795 fixes2 featuresThis release includes various internal improvements, bug fixes across tracing and testing, and an upgrade to React. A new scroll handler is enabled by default for fragment scrolling.
v16.3.0-canary.781 featureThis release introduces an experimental flag for server components HMR cancellation and includes community contributions.
v16.3.0-canary.771 fixThis release focuses on miscellaneous improvements, including avoiding unnecessary validation rendering in development and fixing a SWC compression bug.
v16.3.0-canary.769 fixes1 featureThis release includes numerous bug fixes related to navigation, caching behavior, and CI infrastructure updates. A key change is the prefetching of links nearest the top of the document first.
v16.3.0-canary.751 fix1 featureThis release includes miscellaneous improvements, notably allowing `#/` prefixed subpath imports in Turbopack and enhancing resilience in instant navigation testing.
v15.5.20This release primarily addresses the accidental omission of publishing the @next/swc-wasm-web package, which was last published in version 15.5.15.
v16.2.101 fixThis release primarily addresses the accidental omission of the @next/swc-wasm-web package from the previous publication, ensuring its availability since version 16.2.4.
v16.3.0-preview.54 fixes6 featuresThis release focuses on improving development tooling, particularly around instant navigation prefetching and Turbopack service worker handling. It also includes fixes for image metadata rendering and navigation inspection errors.
v16.3.0-preview.4This release primarily focuses on making the automatic native binding installation an opt-in feature.
v16.3.0-canary.673 fixesThis release restores a previous canary version and includes several bug fixes related to image rendering, navigation inspection, and prefetching warnings. It also updates documentation regarding root parameters.
v16.3.0-canary.661 fixThis release includes several miscellaneous changes, including reverting a previous change to legacy PPR codepaths and fixing dark mode styles for the Navigation Inspector. It also improves CI/CD processes for preview tarballs and canary releases.
v16.3.0-canary.651 fixThis release includes documentation clarifications regarding cache components and prevents mutation of req.headers during internal header stripping. Caches with max memory size 0 will now retain their resolved cache life in development.
v16.3.0-canary.641 fix2 featuresThis release includes miscellaneous improvements, notably adding support for single-entry chunks in Turbopack and introducing a new debugging environment variable.
v16.3.0-canary.633 fixes3 featuresThis release includes improvements to caching mechanisms, such as serving ISR fallback shells on prefetch requests and optimizing navigation locks. It also features various internal cleanups and bug fixes related to instant errors and route parameter computation.
v16.3.0-canary.623 fixes1 featureThis release includes miscellaneous fixes primarily targeting Turbopack stability and resolving false-positive component detection, alongside documentation updates.
v16.3.0-canary.61Breaking3 fixes2 featuresThis release introduces a global opt-in for the runtime stage of Cached Navigations and removes legacy PPR codepaths. It also includes various fixes related to testing, OpenTelemetry attributes, and skill functionality.
v16.3.0-canary.60This release primarily removes the embedded Claude Code plugin marketplace.
v16.3.0-canary.592 fixes1 featureThis release includes an upgrade to swc 70 and introduces more verbose OpenTelemetry spans for the App Router. Several minor fixes address issues related to the after() callback behavior in handlers and actions.
v16.3.0-canary.581 fixThis release includes a fix for dev overlay hydration errors and several internal updates, including a Playwright upgrade and React version bump.
v16.3.0-canary.573 fixesThis release focuses on various fixes, including improvements to the development overlay, Instant Navs DevTools, and documentation updates, alongside an example update for Ably integration.
v16.3.0-canary.561 fix1 featureThis release focuses on improving PR description generation by LLMs and refining error logging by preventing the re-logging of server-originated errors forwarded from the browser.
v16.3.0-canary.551 fixThis release primarily addresses an issue in the release train process by ensuring it continues even if publishing specific WASM packages fails.
v16.3.0-canary.535 fixes2 featuresThis release focuses on internal improvements, including Rust React Compiler updates for React 18 support, various testing stability fixes, and enhancements to OpenTelemetry attribute handling and Turbopack internals.
v16.3.0-canary.522 fixes1 featureThis release upgrades the core build tool to rspack 2.0 and introduces experimental React compiler support in Turbopack, alongside several minor fixes and documentation updates.
v16.3.0-canary.511 fixThis release focuses on a minor improvement to the development rendering experience by preventing a brief Suspense fallback flash during streaming.
v16.3.0-canary.501 fix1 featureThis release includes various internal optimizations for Turbopack, improved handling of streaming prerenders, and a fix for 'this' context in edge sandbox timers. It also introduces support for root parameters in the App Shell client.
v16.3.0-canary.492 fixes3 featuresThis release includes various internal refactorings, improvements to dev server caching behavior, and fixes related to header stripping and dynamic rendering requests. Developers are warned about using prefetch={true} without Partial Prefetching in development.
v16.3.0-canary.483 fixes2 featuresThis release enables turbopack file system caching by default in non-stable builds and introduces a cold cache development indicator. It also includes several minor fixes related to caching, CI processes, and stream handling.
v16.3.0-preview.31 featureThis release focuses on internal continuous deployment improvements, enabling Turbopack caching by default in previews, and setting up the 16.3.x preview release branch.
v16.2.9This release is an empty update intended solely to reset NPM dist-tags, which is required because Trusted Publishing prevents direct tag manipulation.
v16.2.8This release was published specifically to correct the 'next@latest' tag to point to a stable release instead of a prerelease version.
v16.3.0-canary.473 fixes2 featuresThis release focuses on stabilizing several features, including `unstable_instant`, `catchError`, and `retry`, alongside various bug fixes and documentation updates. A key change is renaming the prefetch option `force-runtime` to `allow-runtime`.
v16.3.0-preview.2This release includes a minor change ensuring WASM binaries are tagged correctly.
v16.3.0-preview.1This release introduces the capability to publish preview releases using the @preview NPM dist-tag. It also includes acknowledgments for contributors.
v16.3.0-preview.02 fixes1 featureThis release introduces stabilization for the `prefetch` export and includes several fixes related to streaming, edge bundles, and navigation inspection. A configuration option was also renamed.
v16.3.0-canary.461 fix1 featureThis release removes the deprecated `experimental.useNodeStreams` flag, enables eviction by default, and includes various documentation clarifications and CI improvements.
v16.3.0-canary.451 fix2 featuresThis release introduces global configuration for Partial Prefetching, defaulting it to App Shell only, and includes various internal improvements and fixes related to Turbopack and CNA setups.
v16.3.0-canary.44Breaking2 featuresThis release focuses on internal cleanup and experimental feature enablement within Turbopack, notably removing dead configuration and adding an experimental eviction option.
v16.3.0-canary.43This release reverts a previous change to the test concurrency setting and includes acknowledgments for contributors.
v16.3.0-canary.421 fix2 featuresThis release includes several internal refactorings and improvements for Turbopack, such as treating local const assignments as side-effect free and updating vendored dependencies. React was also upgraded.
v16.3.0-canary.411 fix1 featureThis release includes miscellaneous improvements such as making a function inlinable, staging shell rendering in App Shells, and fixing an issue with the React debug channel on Node streams.
v16.3.0-canary.401 fix3 featuresThis release includes several refactorings, documentation updates, and minor bug fixes, notably addressing build hangs related to sync IO aborts and deprecating undocumented server methods.
v16.3.0-canary.391 fixThis release includes an upgrade to the internal React dependency and a fix for Turbopack's index normalization in debug builds.
v16.3.0-canary.384 fixes2 featuresThis release includes various internal improvements, performance optimizations in Turbopack, and fixes related to caching and debugging channels. Node streams are now enabled by default.
v16.3.0-canary.373 fixes1 featureThis release includes internal Turbopack analyzer improvements regarding floating-point number handling and tracing visualization, along with dependency updates and minor fixes to instrumentation setup.
v15.5.191 fixThis release backports essential bug fixes, notably ensuring FormData entries are preserved. It does not contain the full set of features available on the canary branch.
v16.2.79 fixes2 featuresThis release backports critical bug fixes primarily targeting stability and correctness issues related to routing, caching, server actions, and Turbopack hashing for version 16.2.x.
v16.3.0-canary.361 fix1 featureThis release includes several internal improvements to the Turbopack analyzer, such as better handling of constants and code structure refactoring, alongside a fix for CLI error reporting during type generation.
v16.3.0-canary.35This release includes several internal optimizations and refactorings within Turbopack, such as shrinking data structures and reorganizing analyzer code.
v16.3.0-canary.342 fixes3 featuresThis release includes several internal Turbopack cleanups, documentation updates, and enhancements to developer tooling like the instant error overlay. A key change involves renaming an internal function for short-circuit evaluation.
v16.3.0-canary.333 fixes2 featuresThis release includes streaming prerendering capabilities and various fixes for Turbopack's module analysis and caching behavior. It also addresses an issue with 'use cache' bail-out when unstable_instant is false.
v16.3.0-canary.322 fixesThis release primarily focuses on bug fixes within the Turbopack analyzer related to short-circuit evaluation and module type handling, alongside general maintenance.
v16.3.0-canary.312 fixesThis release includes various internal improvements, CI configuration updates, and fixes for caching and Turbopack analysis. Key changes involve upgrading React and ast-grep, and refining CI token names.
v16.3.0-canary.301 fix1 featureThis release reverts a previous refactoring in the pages router export files and includes client-side prefetching for App Shells. It also resolves a refresh loop issue in Firefox development mode for streaming pages.
v16.3.0-canary.291 fix1 featureThis release introduces persistence for login state in development loops and updates internal optimization components, alongside a fix for error code merging.
v16.3.0-canary.28This release primarily involves internal housekeeping by marking backport-pr and create-pr as internal within the Skills section. It also includes a credit to a contributor.
v16.3.0-canary.272 fixes3 featuresThis release introduces new developer loop and optimization skills, alongside fixes for pagination and metadata prerendering. A key change involves migrating webdriver callers to next.browser.
v16.3.0-canary.262 fixes6 featuresThis release introduces several new experimental features enabled by default, improves Turbopack stability during development, and updates the underlying Rust toolchain.
v16.3.0-canary.256 fixes1 featureThis release includes several fixes and improvements for Turbopack, updates to developer tooling like devlow-bench, and introduces an experimental feature flag for appShells.
v16.3.0-canary.242 fixes5 featuresThis release introduces new configuration options like nextConfig.instrumentationClientInject and enhances debugging tools with MCP compile_route and memory sampling. It also resolves a cross-parameter leak issue related to prefetching and cached navigations.
v16.3.0-canary.233 fixes1 featureThis release introduces an experimental graph-based CSS chunking algorithm in Turbopack and includes several internal improvements and bug fixes related to asset emission and error handling.
v16.3.0-canary.22This release includes a minor internal change in turbo-tasks to prioritize recomputed tasks based on Recomputation priority.
v16.3.0-canary.211 fix1 featureThis release introduces a redesigned development overlay for better developer experience and fixes tracing issues within the webpack NFT pipeline.
v16.3.0-canary.2018 fixes8 featuresThis release focuses heavily on Turbopack improvements, error surfacing in development, and various bug fixes across routing, caching, and server actions. A configuration flag, `partialFallbacks`, has been removed.
v16.3.0-canary.191 featureThis release introduces a proof of concept for task eviction after snapshot within the turbo-tasks-backend.
v16.3.0-canary.181 fixThis release focuses on core improvements by removing a redundant prefetch header and refining error reporting logic in Instant Insights, alongside general CI speed enhancements.
v16.3.0-canary.175 fixes1 featureThis release stabilizes core I/O functionality, introduces a new configuration option for Turbopack chunk loading, and includes several fixes across devtools, routing, and tracing.
v16.3.0-canary.161 fix1 featureThis release introduces an enhancement to cache signal handling during foreground revalidation and fixes an issue with encoding non-ASCII characters in cache tags.
v16.3.0-canary.152 fixes1 featureThis release introduces forced ANSI colors for devtools overlay code frames and includes several Turbopack improvements, such as fixing middleware matchers and tracking proxy access on searchParams.
v15.5.1812 fixesThis release primarily focuses on applying critical security fixes across various components, including Server Components, Middleware, and the Image Optimization API, addressing multiple high and moderate severity advisories.
v16.2.612 fixesThis release primarily focuses on addressing numerous high, moderate, and low-severity security vulnerabilities across Server Components, Middleware, Caching, and Image Optimization. Users are strongly encouraged to update immediately to patch these critical issues.
v16.3.0-canary.14This release focuses on performance improvements, specifically shrinking JsValue size, and internal ordering adjustments for loader tree imports and Turbopack setup.
v16.3.0-canary.131 fixThis release focuses on core improvements by disabling instant validations in draft mode and making internal turbopack optimizations.
v16.3.0-canary.123 fixes1 featureThis release includes core refactoring to decouple request store creation and introduces support for configuring a default instant validation level. Several improvements and fixes were also made within Turbopack.
v16.2.512 fixesThis release primarily focuses on addressing multiple high, moderate, and low severity security vulnerabilities across Server Components, Middleware, Image Optimization, and caching mechanisms. Users are strongly encouraged to update immediately to mitigate these security risks.
v15.5.1612 fixesThis release primarily focuses on addressing multiple security vulnerabilities across Server Components, Middleware, Image Optimization, and caching mechanisms. Users are strongly encouraged to update immediately to mitigate risks.
v16.3.0-canary.113 fixesThis release focuses on bug fixes related to development mode navigation, client-side URL parsing, and Turbopack's import handling. It also updates documentation for unstable APIs.
v16.3.0-canary.102 fixes1 featureThis release includes core updates like React upgrade and improved error handling for next/image, alongside fixes for snapshot coordination races in the backend.
v16.3.0-canary.9This release focuses on internal optimizations by removing the dependency on the once_cell crate across direct dependencies and replacing Lazy<FxHashMap> static lookups with phf::Map.
v16.3.0-canary.82 fixes1 featureThis release reverts a previous change related to Node.js streams and fixes streaming issues in draft mode for cache components, while also adding support for non-standard directives in robots.ts metadata.
v16.3.0-canary.71 fixThis release focuses on miscellaneous improvements, including preserving Playwright traces on failure and fixing crashes in deploy tests related to AI coding assistants.
v16.3.0-canary.64 fixes4 featuresThis release introduces new features like honoring route-level expire values and enabling server HMR for metadata routes, while also deprecating the edge runtime.
v16.3.0-canary.55 fixes1 featureThis release focuses on core stability, improving build performance via Turbopack optimizations, and fixing several bugs related to route handlers and HMR flickering. Sourcemaps are now applied by default during prerendering.
v16.3.0-canary.41 fix1 featureThis release focuses on preserving error codes during page handoffs and optimizing performance by reducing allocations in a specific transform.
v16.3.0-canary.313 fixes8 featuresThis release includes core improvements like strengthening RSC cache-busting, blocking out-of-band client fetches in `instant()`, and various Turbopack enhancements. Several CI/CD processes were updated, including switching to GitHub runners and adopting OIDC for authentication.
v16.3.0-canary.2This release includes minor improvements to tracing attributes for root node creation and enhanced CI tracking for SWC native binary size.
v16.3.0-canary.11 fix2 featuresThis release introduces enhanced prefetch configuration support and improves the handling of concurrent 'use cache' invocations. It also includes a redesign of the blocking route dev overlay and build errors, alongside removing prefetch from instant config.
v16.3.0-canary.02 fixesThis release includes performance optimizations across Turbopack components and fixes an issue with image response body limits. A flag guarding unstable I/O functionality has also been removed.
v16.2.1-canary.465 fixes2 featuresThis release introduces support for type cast expressions in static info extraction and enables prefetchInlining by default. It also includes several fixes related to hydration, devtools overlays, and turbo-tasks performance.
v16.2.1-canary.451 fix1 featureThis release introduces the ability to override outputHashSalt in modifyConfig and restores lld usage for Turbopack on ARM64 glibc Linux.
v16.2.1-canary.441 fixThis release includes a fix for trace-server port conflicts and several internal improvements and refactors within Turbopack's analysis and error reporting. Documentation updates were also made regarding instant navigation and ESLint rules.
Common Errors
TurbopackInternalError4 reportsTurbopackInternalError generally arises from problems with file system access, particularly issues with symlinks, incorrect paths, or restricted permissions during the build process. Ensure your project's file paths, including outputFileTracingRoot, are valid and accessible, and that symlinks within your `node_modules` or project directory are correctly resolved and do not point outside of the project root; consider using the `realpath` command to normalize paths. If using Windows, verify adequate permissions for file operations and consider disabling developer mode or enabling long path support if symlink creation faces issues.
ChunkLoadError3 reportsChunkLoadError in Next.js usually occurs due to mismatched or missing chunks during runtime, often after a deployment where the client-side code expects specific chunk versions that are no longer available on the server. To fix this, ensure consistent chunk generation and caching by clearing your browser cache, employing a service worker to handle asset updates gracefully, and verifying your deployment process accurately reflects the built assets from your Next.js build. Consider using a proper cache invalidation strategy linked to your deploy process.
NoFallbackError1 reportThe "NoFallbackError" in Next.js usually arises when a dynamic route is accessed with a parameter not generated during build time (when `fallback: false` or `fallback: 'blocking'` and the page isn't statically generated) and doesn't exist in your statically generated pages. To fix this, either include the missing parameter as a statically generated route using`getStaticPaths`, configure `fallback: true` to serve a fallback page while the route is generated, or use `fallback: 'blocking'` to block the browser until the route is generated for the first time. Using `fallback: true` or `'blocking'` requires handling the `router.isFallback` state in your component.
CustomApiError1 reportCustomApiError often arises in Next.js due to multiple instances of the same error class being created across different bundles or environments (server vs. client), causing `instanceof` checks to fail. Ensure your custom error class is defined in a single, shared module and is imported from the same absolute path consistently throughout your application, which will prevent module duplication and restore proper `instanceof` behavior. Consider using a bundler analyzer to identify and eliminate duplicate modules if necessary.
CanaryOnlyError1 reportThe "CanaryOnlyError" in Next.js often arises when a component marked with `cache: 'no-store'` or similar cache-busting techniques is unexpectedly cached due to naming conflicts with reserved route parameters like `segments`. To fix this, rename route parameters (e.g., change `segments` to `mySegments`), or avoid using reserved words to prevent unintended caching and ensure your `no-store` directive is respected, thereby preventing cache misses. Ensure these changes are made in both route definitions and component logic.
Related Frontend & Mobile Packages
The library for web and native user interfaces.
Flutter makes it easy and fast to build beautiful apps for mobile and beyond
A framework for building native applications using React
:electron: Build cross-platform desktop apps with JavaScript, HTML, and CSS
Build smaller, faster, and more secure desktop and mobile applications with a web frontend.
FastAPI framework, high performance, easy to learn, fast to code, ready for production
Subscribe to Updates
Get notified when new versions are released