Next.js Daily: Segment Cache Bug Fix and Build Tool Repair
The Next.js team merged fixes for a segment cache issue with unresolved promises and a build crash when using debug paths with parallel routes. Version 16.2.0-canary.57 has been released.
Duration: PT1M26S
Transcript
Good morning. This is Next.js Daily for February 22nd, 2026.
Zack Tanner merged a critical segment cache fix addressing an issue where unresolved promises in RSC responses from prefetches cause Suspense boundaries to remain in fallback state indefinitely. The pull request adds comprehensive test coverage proving this regression, which appears to stem from an underlying React bug rather than Next.js itself. The issue has been addressed upstream in React pull request 35839.
Jiwon Choi merged a fix for a build tool crash that occurred when running `next build --debug-build-paths` on projects with parallel routes. The problem arose from a mismatch between how Turbopack and JavaScript route discovery filter routes, causing undefined lookups in the app paths manifest. The fix adds proper guards to skip non-existent manifest entries.
The team also released version 16.2.0-canary.57, updating package versions across the entire Next.js ecosystem including create-next-app, ESLint configurations, and various Next.js plugins.
What's next: These fixes improve stability for segment caching and build tooling, particularly for projects using parallel routes and advanced prefetching patterns. Developers using debug build paths should see immediate improvements.
That's your Next.js update for today.