Next.js
Frontend & MobileThe React Framework
Release History
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.
v16.2.0-canary.982 featuresThis release focuses on improvements to partial fallbacks, enhancing how shells are upgraded and completed. It also includes minor cleanup in documentation and build scripts.
v16.2.0-canary.971 fix2 featuresThis release introduces new build diagnostics via route bundle stats and exposes edge runtime fields in build-complete. Turbopack updates include switching chunk/asset hashes to base40 encoding and fixing polyfill emission for API routes.
v16.2.0-canary.964 fixes2 featuresThis release focuses on performance improvements, such as optimizing base64 encoding, and various internal cleanups including renaming structs in Turbopack and improving test stability. It also introduces server-side hints for Prefetch Inlining.
v16.2.0-canary.95Breaking1 fix3 featuresThis release includes core updates like exposing server router helpers and hydrating instant navigation tests, alongside the removal of the LMDB backend from turbo-tasks-backend.
v16.2.0-canary.942 fixes1 featureThis release introduces build-time validation for Instant and includes several internal dependency bumps and minor fixes, notably related to TypeScript transforms in TURBOPACK.
v16.2.0-canary.931 fix2 featuresThis release introduces a Start button for Instant Navs inspection and preserves RSC metadata in proxy requests. It also includes a fix related to ThreadsafeFunctions in turbopack to ensure proper Node.js exit after builds.
v16.2.0-canary.922 fixes2 featuresThis release introduces rendering code frames on the Turbopack side and adds an experimental configuration option for Lightning CSS features. Several internal improvements and bug fixes related to sorting and tracing were also implemented.
v16.2.0-canary.912 featuresThis release introduces performance improvements and new features within the Turbopack integration, specifically around fixed key blocks and task storage encoding.
v16.2.0-canary.902 fixesThis release includes a fix for legacy browser support by rewriting the MiniCssExtractPlugin insert function to ES5 and addresses an issue with pnpm binary creation. It also includes documentation updates for Server Actions security and streaming.
v16.2.0-canary.891 featureThis release includes updates to Instant Navs devtools and enhances trace uploads with git and environment information.
v16.2.0-canary.865 fixes2 featuresThis release focuses on improving Turbopack's HMR capabilities, enhancing error reporting, and fixing various bugs related to URL normalization and build scripts.
v16.2.0-canary.881 featureThis release introduces a new condition, ReferenceTypeCondition, within Turbopack.
v16.2.0-canary.852 fixes1 featureThis release includes documentation fixes, resolves an issue with next-routing header interpolation, and updates Turbopack to accept ChunkGroup in entry_chunk_group.
v16.2.0-canary.841 fixThis release focuses on core stability improvements, including bumping the Node heap limit for linting and upgrading the internal React version. A fix was also implemented for server action redirects during build ID mismatches.
v16.2.0-canary.835 fixes2 featuresThis release focuses on core improvements, including rewriting instant validation and caching runtime data for partially static pages. It also introduces the `experimental.cachedNavigations` flag and various Turbopack enhancements.
v16.2.0-canary.82This release includes miscellaneous changes, specifically setting DontFork and Unmergeable flags on all mmap sites within turbo-persistence, and acknowledges a contributor.
v16.2.0-canary.813 fixes1 featureThis release includes core updates such as upgrading React, fixing build failures related to prefetch inlining, and adding trace spans for turbopack persistence. It also contains various Turbopack improvements and bug fixes.
v16.2.0-canary.80This release focused on internal code quality improvements, specifically addressing review feedback by extracting modules and cleaning up imports.
v16.2.0-canary.791 featureThis release introduces an adapter flag for partial fallbacks and updates CI configurations for GitHub authentication status checks.
v16.2.0-canary.781 fix4 featuresThis release focuses heavily on improving navigation caching by implementing caching for static and runtime stages of pages. It also removes significant legacy code related to PPR (Partial Page Rendering).
v16.2.0-canary.771 featureThis release focuses on core improvements, including updated default error pages and a new, allocation-free hasher implementation for Turbopack.
v16.2.0-canary.75This release includes miscellaneous internal updates, such as updating the Rspack development test manifest and changing how storage keys are generated.
v16.2.0-canary.742 fixes2 featuresThis release includes core refactoring, an upgrade to React, and improvements to turbo-persistence with CRC32 checksums and error handling.
v16.2.0-canary.731 fix3 featuresThis release includes core changes like stubbing adapterPath, performance improvements in turbo-persistence, and new features for the pr-status CLI tool. It also addresses a CSS restriction issue in the Pages Router.
v16.2.0-canary.72This release includes documentation updates for the error component unstable_retry() and various internal improvements to Rspack and Turbopack testing manifests and linting rules.
v16.2.0-canary.712 fixes2 featuresThis release includes several core improvements, notably fixing path handling on Windows within Turbopack and updating the React Compiler version. It also introduces new configuration options for the Docker example and publishes @next/playwright to npm for canary releases.
v16.2.0-canary.701 fix2 featuresThis release introduces improved prefetching capabilities and fixes an issue with cookie handling during fresh page loads. It also updates internal tooling for better development workflow.
v16.2.0-canary.692 featuresThis release introduces an experimental configuration option for swapping the Turbopack backend and reverts the default loader runtime backend to child processes for stability. It also includes memory optimizations via a streaming SST writer.
v16.2.0-canary.682 fixes1 featureThis release focuses on core improvements in Turbopack HMR behavior and stability fixes in the testing infrastructure, including resolving CI shard divergence.
v16.2.0-canary.671 fixThis release primarily focuses on internal testing improvements by restricting the main test mode execution to custom deploy scripts. Thanks to @ijjk for contributions.
v16.2.0-canary.662 fixes6 featuresThis release focuses on core infrastructure improvements, including Turbopack execution via napi/worker_threads and support for Node.js experimental inspector flags in development and build processes. Several internal refactors and documentation fixes were also implemented.
v16.2.0-canary.65Breaking1 fixThis release introduces a panic in Turbopack for top-level eventually consistent reads and fixes a middleware issue with adapters. It also improves HMR source mapping in the Turbopack server.
v16.2.0-canary.641 fix1 featureThis release focuses on core improvements, including a fix for the edge index page data route and an enhancement to Turbopack server HMR with a restart event.
v16.2.0-canary.634 fixes2 featuresThis release includes several core improvements, notably enabling `experimental.reactDebugChannel` by default and fixing issues related to prefetching and devtools reporting. It also updates the internal React version.
v16.2.0-canary.62Breaking7 fixes2 featuresThis release introduces instant serving for cached navigations and enforces the use of `unstable_instant` only in Server Components. Several core fixes address worker compatibility, suspense boundaries, and server patching behavior.
v16.2.0-canary.612 fixes2 featuresThis release focuses on core stability, fixing an issue with parameter leakage in development navigation, and introduces a new testing helper package for Playwright.
v16.2.0-canary.605 fixes1 featureThis release includes fixes for route caching, image handling, and Webpack profiling configuration, alongside an upgrade to React and improvements to documentation.
v16.2.0-canary.591 fixThis release includes internal refactoring for Turbopack, fixes an issue where the Image component ignored quality settings in Jest, and updates several internal dependencies and documentation.
v16.2.0-canary.581 fixThis release primarily addresses a crash related to route replacement under debug build paths and includes minor updates to statistics comments.
v16.2.0-canary.571 fix1 featureThis release introduces Subresource Integrity support in Turbopack and includes a test fix related to the segment cache context provider.
v16.2.0-canary.562 fixesThis release includes fixes for runtime prefetch byte stripping and sync IO validation, alongside an example migration from react-markdown to Streamdown static.
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.
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