What vercel/next.js shipped
Written by FoxPlug from the repository's own releases; not affiliated with Next.js. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/vercel/next.js; Next.js did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of October 5, 2026
What shipped
- Released v16.5.0-canary.8 with fixes for error message formatting in the server error inspector and removal of the webp feature flag in Turbopack. Release
- Enabled garbage collection by default on canary to prevent the filesystem cache from growing over time and improve read performance. Pull request #99596
- Fixed two Turbopack garbage collection bugs that could leave half-torn-down dependency edges and cause panics when GC and persistent caching are both enabled. Pull request #99902
- Relanded experimental custom webpack support with next dev --custom-webpack and next build --custom-webpack CLI options. Pull request #99234
- Improved error messages when Node.js worker processes cannot connect to Turbopack with a dedicated exit code for better debugging. Pull request #99887
- Exposed next/image-optimizer-transform as a public subpath so services can import the image optimizer transform without relying on internal file layout. Pull request #99312
- Added zstd compression flags for NEXT_TURBOPACK_TRACING including zstd, zstd-fast, and zstd-best options for trace file compression. Pull request #99808
- Released v16.5.0-canary.7 with experimental custom webpack support and upgrades to Corepack, Turborepo, and pnpm cache handling. Release
Why it matters
This week focused on Turbopack reliability and performance improvements, including garbage collection fixes and better error handling for developer experience. The project also improved cache handling across package managers and restored custom webpack support for users who need it.
Changelog entry
- Fixed error message formatting in server error inspector to not parse error message lines as stack frames Release
- Removed webp feature flag from Turbopack, always building with webp enabled Pull request #99964
- Enabled garbage collection by default on canary builds Pull request #99596
- Fixed two Turbopack GC bugs that could leave half-torn-down dependency edges Pull request #99902
- Improved error messages when Node.js worker processes cannot connect to Turbopack Pull request #99887
- Fixed Turbopack to ignore realpath errors during module resolution, matching Node.js behavior Pull request #99951
- Relanded experimental custom webpack support with CLI options Pull request #99234
- Reduced build tree view memory allocations by writing route previews directly to output Pull request #99930
- Exposed next/image-optimizer-transform as public subpath for external image optimizer services Pull request #99312
- Added zstd compression options for NEXT_TURBOPACK_TRACING Pull request #99808
- Upgraded Corepack to 0.34.7 for pnpm 12 compatibility Pull request #99959
- Upgraded Turborepo to 2.11.7 to support pnpm 12 lockfile format Pull request #99958
V16.5.0-canary.8 ships error message formatting fixes, enables garbage collection by default, and removes the webp feature flag from Turbopack. Garbage collection helps keep filesystem caches lean for faster builds.
Next.js canary releases this week bring several reliability improvements: garbage collection now enabled by default to prevent cache bloat, fixes for Turbopack GC dependency edge issues, and restored experimental custom webpack support. We also improved error reporting when worker processes fail to connect and exposed the image optimizer transform as a public API. These changes help developers get more predictable build performance and better debugging feedback.
Week of September 28, 2026
What shipped
- Fixed unnecessary Suspense fallback triggered by URL updates when router state changes were not wrapped in startTransition for restore operations. Pull request #99612
- Fixed client params suspension on shallow URL updates so pages reading use(params) or use(searchParams) no longer show Suspense fallback on history.pushState or history.replaceState. Pull request #99611
- Added reactCompiler.enablePreserveExistingMemoizationGuarantees option to preserve memoization guarantees through Babel and Turbopack Rust compiler paths. Pull request #98589
- Added route summary homepage to Turbopack bundle analyzer with precomputed bundle sizes for every route in /analyze view. Pull request #98787
- Added warning when cacheComponents is enabled without explicit partialPrefetching setting to guide users on configuration. Pull request #99452
- Optimized ESM exports by shifting protocol burden to getters, reducing bundle size for the 90% of exports that are values. Pull request #98932
- Allowed opt-in facade-backed export mangling for applications that benefit from shorter keys while keeping local-only modules unsplit by default. Pull request #99309
- Moved App Page header parsing to handler entrypoints to decouple App Router rendering from incoming request objects. Pull request #99506
- Unified bundle analyzer delta colors using shared blue and amber theme tokens for bundle growth and shrinkage across compare views. Pull request #99607
- Added async module scope display in bundle analyzer single-build view with filtering and legend to distinguish sources behind async import boundaries. Pull request #98918
Why it matters
This week focused on improving the developer experience with router stability fixes that prevent unnecessary UI fallbacks during navigation, enhanced bundle analysis capabilities to help developers understand code splitting, and optimizations that reduce bundle sizes. These changes address common pain points in App Router apps and make it easier to diagnose performance issues.
Changelog entry
- Fixed unnecessary Suspense fallback triggered by URL updates in App Router by wrapping router state restores in startTransition Pull request #99612
- Fixed client params suspension on shallow URL updates (history.pushState/replaceState) when using use(params) or use(searchParams) Pull request #99611
- Added reactCompiler.enablePreserveExistingMemoizationGuarantees configuration option for React Compiler Pull request #98589
- Added route summary to Turbopack bundle analyzer with precomputed sizes and /analyze route for detailed analysis Pull request #98787
- Added warning when cacheComponents is enabled without explicit partialPrefetching configuration Pull request #99452
- Optimized ESM exports by shifting protocol burden to getters, reducing overhead for value exports Pull request #98932
- Unified bundle analyzer delta colors with shared theme tokens for bundle growth and shrinkage visualization Pull request #99607
- Added async module scope labeling and filtering in bundle analyzer to distinguish sources behind async boundaries Pull request #98918
- Moved App Page header parsing to handler entrypoints to decouple rendering from request objects Pull request #99506
- Enabled opt-in facade-backed export mangling for applications benefiting from shorter export keys Pull request #99309
V16.4.0-canary updates: fixed URL update Suspense fallbacks, added async scope in bundle analyzer, optimized ESM exports, and improved router param handling.
This week's Next.js canary releases focused on improving navigation stability and bundle analysis. We fixed unnecessary Suspense fallbacks when updating URLs with shallow changes, added async module scope visibility in the bundle analyzer to help identify code-splitting opportunities, optimized ESM exports to reduce bundle sizes, and improved how the App Router handles parameter updates. These changes help developers build faster apps with better visibility into their bundles.
Week of September 21, 2026
What shipped
- V16.4.0-canary.51 released with security upgrade insights in DevTools and focused npm advisories. Release
- Developers running next dev with agentic auto-upgrade enabled now see browser reminders when their Next.js version has a security advisory. Pull request #99002
- Advisory checks now query only the installed version and upgrade candidates instead of sending bulk audit requests. Pull request #99222
- V16.4.0-canary.50 released with prerelease security upgrade support and agentic upgrades without Git. Release
- Apps without a Git repository can now use agentic upgrades by checking for duplicate work using available repository capabilities. Pull request #99217
- Dynamically imported local-only ESM modules no longer create duplicate runtime identities through facade splits. Pull request #99285
- Fixed Server Actions hanging after navigation to PPR pages by properly handling postponed state in POST requests. Pull request #99252
- Edge App Router SSR now respects the same metadata streaming policy as Node SSR for user-agent-based bot requests. Pull request #99128
- V16.4.0-canary.46 released with experimental custom webpack support reverted and Turbopack improvements. Release
- CI for branch-based PR stacks now uses a read-only TypeScript gate instead of Graphite-specific optimization. Pull request #99086
Why it matters
This week's changes focus on security upgrade workflows, PPR page navigation reliability, and metadata streaming correctness. Developers get better visibility into security advisories and can upgrade without Git, while builds become more robust with fixes to ESM module loading and Edge SSR metadata handling.
Changelog entry
- Show security upgrade insights in DevTools Release
- Use focused npm advisories and nudge only for ready upgrades Pull request #99222
- Explain prerelease security upgrade limits Pull request #99230
- Support latest agentic upgrades on prerelease channels Pull request #99223
- Allow agentic upgrades without Git Pull request #99217
- Avoid facade splits solely for export mangling Pull request #99285
- Allow webpack loaders to cross filesystem roots when reading dependencies Pull request #99202
- Fix Server Actions hanging after navigation to PPR pages Pull request #99252
- Respect metadata streaming policy in Edge SSR Pull request #99128
- Revert experimental custom webpack support Pull request #99227
V16.4.0-canary.51 ships security upgrade insights in DevTools, npm advisory improvements, and PPR page navigation fixes. Agentic upgrades now work without Git.
V16.4.0-canary.51 brings security upgrade insights directly into DevTools with focused npm advisories. Developers can now use agentic upgrades even without Git, and we've fixed Server Actions hanging on PPR page navigation. Edge SSR now properly respects metadata streaming policies, and ESM module loading is more reliable.