Change8

Next.js

Frontend & Mobile

The React Framework

Latest: v16.4.0-canary.1225 releases10 common errorsView on GitHub

Release History

View all versions →
v16.4.0-canary.12
Aug 29, 2026

This release includes miscellaneous changes such as removing a popular workflow, storing keys in SST blocks, honoring non-interactive mode in upgrade codemod prompts, and transforming .mjs files with Next.js codemods.

v16.4.0-canary.114 fixes4 features
Aug 28, 2026

This release includes several Turbopack improvements, such as enabling export mangling by default for smaller bundle sizes and adding a new getter for experimental React features. It also addresses various bug fixes related to routing and filesystem operations.

v16.4.0-canary.102 fixes2 features
Aug 28, 2026

This release includes several Turbopack improvements, a new option for caching components in create-next-app, and deprecates React 18 support for the Pages Router. It also addresses various bug fixes and CI/testing enhancements.

v16.4.0-canary.914 fixes3 features
Aug 27, 2026

This release includes various bug fixes, performance improvements in Turbopack, and updates to Rust and React versions. It also introduces new features for stubbing HTTP on WASM targets and improving env var handling.

v16.4.0-canary.83 fixes1 feature
Aug 25, 2026

This release includes improvements to Turbopack's import resolution and TypeScript tracing. It also addresses symlink resolution issues and simplifies the ecmascript effect queue.

v16.4.0-canary.717 fixes
Aug 25, 2026

This release includes various bug fixes across different modules like ISR, next/image, and turbopack. It also addresses documentation issues and stabilizes several tests.

v16.3.32 fixes
Aug 25, 2026

This release addresses critical security vulnerabilities, including unauthenticated remote code execution on Windows-hosted servers and within the Image Optimization API when using AVIF files.

v15.5.242 fixes
Aug 25, 2026

This release addresses critical security vulnerabilities, including unauthenticated remote code execution on Windows-hosted servers and within the Image Optimization API when using AVIF files.

v16.4.0-canary.62 fixes
Aug 24, 2026

This release includes miscellaneous changes focused on improving Turbopack's performance and reliability, such as inline execution of scheduled tasks and better error handling. It also addresses a bug in metadata prefetch cache keys.

v16.4.0-canary.54 fixes
Aug 24, 2026

This release includes miscellaneous improvements such as recording fallback cache lifetime for blocking PPR routes, documenting catchError for the Pages Router, and performance optimizations for Turbopack and TurboMalloc. It also deduplicates several dependencies.

v16.4.0-canary.45 fixes5 features
Aug 24, 2026

This release includes improvements to Turbopack's NFT handling and route emission, alongside bug fixes for async blocks and navigation. The adapter route collapses are now off by default.

v16.4.0-canary.31 fix
Aug 23, 2026

This release includes a bug fix for the devtools indicator dragging on touch screens. It also acknowledges a contributor.

v16.4.0-canary.21 feature
Aug 22, 2026

Introduced an options struct for backend storage construction. Acknowledged contributions from @lukesandberg.

v16.4.0-canary.17 fixes5 features
Aug 21, 2026

This release introduces new features like instant validation for unstable_navigation() and unstable_prefetch(), along with several bug fixes and improvements to Turbopack and testing infrastructure. It also includes documentation corrections and adds a new execution primitive for turbo-tasks.

v16.4.0-canary.01 fix4 features
Aug 21, 2026

This release includes several improvements to Turbopack, such as isolating HMR listeners, deduplicating app chunks, and optimizing symlink handling. It also addresses a bug related to preserving trailing slashes during export MPA fallback.

v16.3.26 fixes
Aug 21, 2026

This release backports several bug fixes to the core functionality, including improvements for Turbopack and Turborepo remote caching.

v16.3.1-canary.263 fixes2 features
Aug 20, 2026

This release introduces experimental navigation features with unstable_navigation() and improves HMR handling. It also includes various documentation updates and test infrastructure improvements.

v16.3.1-canary.259 fixes3 features
Aug 19, 2026

This release includes several bug fixes and improvements to Turbopack, along with documentation updates and miscellaneous changes to enhance stability and performance.

v16.3.1-canary.243 fixes3 features
Aug 18, 2026

This release includes improvements to Turbopack's regex handling and development experience, along with form accessibility enhancements and documentation updates. It also introduces model prerendering as a render candidate.

v16.3.1-canary.234 fixes
Aug 18, 2026

This release includes various miscellaneous changes, primarily focusing on CI improvements, documentation fixes, and test enhancements. It also traces lazy loading for App Route modules.

v16.3.1-canary.226 fixes
Aug 17, 2026

This release includes several miscellaneous changes and bug fixes, primarily focused on turbo-persistence and turbo-tasks-backend improvements, including persistence delete/tombstone plumbing and enforcing task existence.

v16.3.1-canary.211 fix
Aug 16, 2026

This release includes miscellaneous changes such as anchoring async local storage instances to global symbols, deflaking a test case, and scaffolding for a concurrent router queue flag. It also reorganizes client router modules.

v16.3.1-canary.202 fixes
Aug 15, 2026

This release includes several miscellaneous changes, focusing on browser hydration recoveries, metadata resolution, Turbopack behavior, and the removal of the server route matcher stack.

v16.3.1-canary.193 fixes1 feature
Aug 14, 2026

This release introduces SelectedMetadata for improved metadata rendering and includes several bug fixes for Next.js Image and Turbopack, enhancing stability and performance.

v16.3.1-canary.18
Aug 14, 2026

Upgraded React to a newer commit hash. This change primarily affects internal dependencies and build processes.

Common Errors

TurbopackInternalError4 reports

TurbopackInternalError 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.

InvalidCharacterError3 reports

This error, InvalidCharacterError: Invalid character, typically arises in Next.js when route segments or group names contain characters outside the Latin-1 character set, a regression in Next 15. To fix it, ensure all your route segment and group folder names exclusively use standard ASCII characters. Avoid special characters, accents, or non-English alphabets in these directory names to prevent the error.

DOMException3 reports

This DOMException error often arises in Next.js during prerendering when an aborted render retains its V8 stack frames unnecessarily, leading to memory leaks. To fix this, ensure that abort reasons are properly cleared or serialized to avoid holding onto large render graph objects. Implementing mechanisms to discard or prune these stack frames when an abort occurs will significantly reduce memory usage.

ChunkLoadError3 reports

ChunkLoadError 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.

RangeError3 reports

This RangeError typically occurs when Next.js encounters a very large module path during development, exceeding internal buffer limits. To fix this, ensure your project dependencies are up-to-date and consider upgrading to the latest stable version of Next.js, as recent versions often include performance improvements and bug fixes for module resolution. If the issue persists, examine your project structure for unusually long file paths or deeply nested node_modules directories.

SuspenseException2 reports

This error typically occurs in next-js. Check the example issues for common solutions.

Related Frontend & Mobile Packages

Subscribe to Updates

Get notified when new versions are released

RSS Feed