Next.js
Frontend & MobileThe React Framework
Release History
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.
v16.2.44 fixesThis release focuses on backporting critical bug fixes, including resolving issues with Google Fonts on Windows ARM64 and improving Turbopack's filesystem watcher and task execution stability.
v16.2.1-canary.432 fixes5 featuresThis release focuses on core stability, performance improvements like a fast path for trace() when OpenTelemetry is disabled, and various internal refactorings within Turbopack, including fixing issues with SWC plugin paths and monorepo binaries.
v16.2.1-canary.423 fixesThis release focuses on core improvements, including scoping the Safari cache-buster, enabling WASM plugins on Windows ARM, and fixing a build crash related to prefetch inlining on notFound() pages.
v16.2.1-canary.411 fixThis release primarily contains a minor fix related to the devlow-bench configuration.
v16.2.1-canary.401 fixThis minor release includes a fix for the turbo cache flag, ensuring it correctly uses the --force option.
v16.2.1-canary.381 fixThis release focuses on a core change ensuring the x-nextjs-data header is correctly scoped only to resolve operations. Special thanks to @ijjk for their contribution.
v16.2.1-canary.37Breaking1 fixThis release focuses on build improvements by excluding trace files from deletion and adjusting the HTTP response code for segment prefetch cache misses from 204 to 404. SCCache has also been re-enabled.
v16.2.1-canary.361 fixThis release primarily addresses a bug related to prefetch hint loading during revalidation.
v16.2.1-canary.354 fixes3 featuresThis release includes compiler improvements for defining primitives, enhanced Turbopack compatibility with Vite's import.meta.glob, and several bug fixes related to server actions and dependency updates.
v16.2.1-canary.341 featureThis release introduces error recovery improvements for Node.js streams and includes various internal cleanups and documentation clarifications.
v16.2.1-canary.331 fix2 featuresThis release introduces new configuration resolution in Turbopack and improves accessibility in the segment explorer. It also includes internal cleanups and performance optimizations.
v16.2.1-canary.323 fixes2 featuresThis release introduces improvements to path resolution in tsconfigs and enhances Node.js stream handling with a new forkpoint for CacheComponents. It also includes several stability fixes and dependency upgrades, notably bumping swc to 63.1.1.
v16.2.1-canary.311 fixThis release fixes an issue where strings thrown in Server Components were being swallowed, improving error reporting.
v16.2.1-canary.305 fixes2 featuresThis release focuses heavily on performance improvements across core functionalities, including faster URL checks, optimized production builds by removing watchpack, and better caching mechanisms in Turbopack. Several minor bugs related to logging, HMR reconnection, and incremental builds have also been resolved.
v16.2.1-canary.292 fixes1 featureThis release includes a core change in Turbopack's token handling and various build information improvements, alongside CI and testing fixes.
v16.2.1-canary.273 fixes3 featuresThis release includes core improvements such as better error messaging for blocking routes and updates to Node.js streams. It also bundles the skills directory and updates several SWC dependencies.
v15.5.15This release addresses a security vulnerability (CVE-2026-23869). Refer to the linked changelog for details on the fix.
v16.2.35 fixesThis release backports critical security and bug fixes, addressing issues in ISR reporting, HMR, asset emission, styled-jsx rendering, and turbo-tasks stability.
v16.2.1-canary.261 fix1 featureThis release focuses on core routing improvements, including better middleware matching and URL normalization, alongside performance enhancements in persistence handling.
v16.2.1-canary.254 fixesThis release focuses on stability and performance improvements, including fixes for styled-jsx race conditions and turbo-tasks crashes. It also enhances developer experience with better warning messages and tooling updates.
v16.2.1-canary.24Breaking1 fixThis release includes an upgrade to pnpm 10.x, dependency bumps for Turborepo, and a key API change in Turbopack replacing `turbo_tasks::apply_effects` with `Effects::apply`.
v16.2.1-canary.231 featureThis release introduces improved parsing for app route strings and includes performance enhancements in the builder via sorted inserts.
v16.2.1-canary.222 fixesThis release includes fixes for route parameter handling and agent discovery, along with improved runtime handling for imports related to node:stream.
v16.2.1-canary.211 featureThis release focuses on internal improvements in next-core by deduplicating output assets and adding conflict detection during emission. Documentation for deploy tests in the contributing guide was also updated.
v16.2.1-canary.20Breaking2 fixes1 featureThis release improves the development server experience with better error messages and automatic restarts, and introduces experimental configuration options for SWC. It also includes several internal Turbopack and turbo-tasks refactorings.
v16.2.1-canary.192 fixes3 featuresThis release introduces a new compilation issues tool and enhances error reporting for stale ISR revalidation. It also marks the 'experimental.useCache' API as deprecated.
v16.2.1-canary.182 fixes2 featuresThis release introduces telemetry for adapter configuration and the first pass of Node.js streams support, alongside several minor fixes and improvements.
v16.2.1-canary.171 fix2 featuresThis release introduces a new environment variable for filename salting and improves stability by fixing a deadlock issue in the task cache. It also includes various documentation clarifications and test stability improvements.
v16.2.23 fixes2 featuresThis release primarily backports bug fixes and minor core changes, including enabling server HMR for app route handlers in Turbopack and addressing TypeScript deprecations.
v16.2.1-canary.161 fix1 featureThis release introduces a new rust-fingerprint task and improves error messaging for deprecated configurations, alongside fixing a CSS HMR bug in Turbopack for Safari users.
v16.2.1-canary.155 fixes2 featuresThis release includes several Turbopack improvements, fixes for URL handling in the cache, and new configuration options for server-side features like Fast Refresh.
v16.2.1-canary.141 fix1 featureThis release includes an update to React and adds the inclusion of route type causes in [ftl]. It also reverts a change related to turbo-tasks hashing.
v16.2.1-canary.13This release includes minor documentation updates and adjusts examples for the revalidateTag function to reflect its new two-argument signature.
v16.2.1-canary.12Breaking2 featuresThis release introduces new offline state management features via the useOffline flag and hook, and includes internal refactoring such as renaming a field in SingleModuleReference and optimizing string usage in napi structs.
v16.2.1-canary.111 featureThis release includes an upgrade to React and Biome 2.4, along with improvements to devtools error reporting and agent rule alignment.
v16.2.1-canary.10Breaking2 fixes1 featureThis release focuses on internal improvements in turbo-tasks and turbopack, including a breaking API change in Vc resolution and enhancements to change detection mechanisms.
v16.2.1-canary.91 featureThis release introduces a change in Segment Bundling to bundle static prefetches based on size. Thanks to @acdlite for contributions.
v16.2.1-canary.81 fix1 featureThis release focuses on performance improvements across core functionality, including skipping unnecessary array conversions and optimizing instrumentation. It also introduces a draggable panel in devtools and updates Turbopack's hash encoding.
v16.2.1-canary.72 fixes1 featureThis release focuses on core improvements, including avoiding deprecated TypeScript module resolution defaults and introducing a new CLI command for Turbopack database compaction.
v16.2.1-canary.61 fix2 featuresThis release focuses on core improvements to Segment Bundling correctness and prefetch tracking, alongside minor documentation updates and test stabilization.
v16.2.1-canary.5This release focuses on minor documentation improvements, specifically ensuring consistent use of the ErrorInfo type within catchError documentation.
v16.2.1-canary.44 fixes2 featuresThis release focuses on various fixes and improvements within the Turbopack ecosystem, including performance enhancements for cross-compiled MUSL and new tracing capabilities.
v16.2.16 fixesThis release focuses on backporting essential bug fixes across core components, including Turbopack, server actions, and metadata handling, while skipping pending feature additions.
v16.2.1-canary.33 fixesThis release focuses on core optimizations and bug fixes, including improvements to layout segment optimization and server actions stability in standalone mode. Turbopack received several performance and tracing enhancements.
v16.2.1-canary.212 fixes4 featuresThis release focuses on core improvements in Turbopack, including enabling server HMR for app route handlers and various stability fixes across testing and backend operations. Several flaky tests were addressed and internal module loading was improved.
v15.5.141 fix1 featureThis release focuses on backporting essential bug fixes, notably restoring headers for JSON responses in the pages router, and introduces an LRU disk cache for next/image.
v16.2.1-canary.11 fix1 featureThis release fixes an issue with Content-Length and ETag headers for pages-router JSON responses and updates the tokio dependency.
v16.2.1-canary.02 fixesThis release updates the vendored lodash dependency to version 4.17.23 to fix CVE-2025-13465 and resolves issues related to RSC requests and dynamic placeholder encoding in app routes.
v16.2.0Breaking26 fixes13 featuresThis release focuses heavily on improving type safety within the App Router via the new `experimental.strictRouteTypes` configuration, alongside numerous stability fixes and performance improvements in Turbopack. It also introduces new developer tooling like CPU profiling and an agents-md command.
v16.2.0-canary.1042 fixes1 featureThis release includes core improvements to Turbopack profiles and validation boundary discovery, alongside minor updates to Turbopack's debugging configuration.
v16.2.0-canary.103Breaking9 fixes2 featuresThis release introduces stability improvements by moving adapter path configuration to stable, fixing several caching and prefetching bugs, and removing the experimental devCacheControlNoCache option.
v16.2.0-canary.1028 fixes2 featuresThis release includes improvements to Turbopack HMR, fixes for caching inconsistencies, and enhanced error reporting for RSC and CSS parsing. Server Actions now have stricter privacy controls for submissions.
v15.5.131 fixThis release focuses on backporting critical bug fixes, specifically addressing a request smuggling vulnerability in http-proxy rewrites.
v16.1.73 fixes2 featuresThis release focuses on backporting critical security fixes and stability improvements, including patching request smuggling and addressing hanging streaming fetches in development.
v16.2.0-canary.1001 fixThis release primarily addresses a CI stability issue by fixing a timeout in the test-cargo-unit job caused by LTO enablement.
v16.2.0-canary.991 fix4 featuresThis release introduces performance improvements in Turboopack analysis and simplifies scroll restoration logic. It also includes minor testing adjustments and core feature enhancements.
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