Next.js Daily: React Upgrade and Memory Leak Fix
Next.js merged 7 pull requests yesterday, including a React upgrade and a critical memory leak fix for prefetch streams. Additional changes address image optimization bugs and system resource management.
Duration: PT1M45S
Transcript
Good morning, it's February 10th, 2026, and you're listening to Next.js Daily.
The Next.js team merged seven pull requests yesterday, starting with a significant React upgrade. The nextjs-bot merged an upgrade from React build 2dd9b7cf to 272441a9, updating over 2,000 lines across 82 files to incorporate the latest upstream changes.
Hendrik Liebau merged a critical fix for memory leaks in browser prefetch streams. The previous implementation kept unclosed ReadableStreams as garbage collection roots in Chrome and Firefox, preventing proper cleanup. This fix leverages React Flight's new unstable_allowPartialStream option to close streams normally while handling unresolved references correctly.
Daniel Tao fixed a bug in image optimization where the findClosestQuality function returned zero for low quality values, causing the server to reject requests with 400 errors. The fix changes the reduce function's initializer from zero to use the first quality value from the configuration array.
Luke Sandberg corrected a min-max confusion in Turbopack's shard amount calculation that treated all systems as 64-core machines and could cause overflow on larger systems.
Niklas Mischkulnig updated manifest loading calls to properly pass the shouldCache parameter to all functions.
The Vercel Release Bot updated both development and production Rspack test manifests with new integration test configurations.
What's next: Watch for the React upgrade effects in canary builds, and monitor memory usage improvements from the prefetch stream fix.
That's your Next.js update for February 10th. I'm your host, and we'll be back tomorrow.