Next.js Daily: Partial Prefetching and Memory Management Overhaul
Next.js introduced a major prefetching behavior change with Partial Prefetching now defaulting to app shell only, while Turbopack enabled memory eviction by default on canary to address resource consumption issues.
Duration: PT2M9S
Episode overview
This episode is a short developer briefing from Next.js Daily.
It explains recent repository work in plain language.
- Show: Next.js Daily
- Published: 2026-06-08T06:04:39Z
- Audio duration: PT2M9S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning, it's June 8th, 2026. Yesterday brought significant changes to Next.js prefetching behavior and memory management that will affect how your applications load and perform.
The biggest change is Partial Prefetching's new default behavior. When enabled, links now only prefetch the app shell by default, not the full page data. This fundamentally changes the performance model - rendering a link is now essentially "free" unless you explicitly set prefetch equals true. For fully static…
Three related pull requests from Andrew Clark implemented this shift. PR 94448 added the global partial prefetching config, PR 94510 changed the default to app shell only, and PR 94489 fixed a critical bug in subtree hint propagation that was discovered during this work. The team also added an "eager" prefetch mode…
Memory management saw equally important updates. Luke Sandberg's work enabled Turbopack memory eviction by default on canary builds through PR 94451, addressing significant memory consumption issues. The foundational work in PR 94173 was particularly complex - it restructured how effects are processed to allow…
Additional improvements included specialized error messages for client…
The…
Nearby episodes from Next.js Daily
- Server Component HMR Performance Overhaul
- Turbopack Performance and Build Pipeline Optimizations
- Runtime Optimization and Stream Performance
- App Shell Rendering and Turbopack Optimizations
- Node Streams Default and Development Experience Improvements
- Turbopack JavaScript Handling and Production Optimizations
- Weekly Recap - Turbopack Analyzer Refactoring and Developer Experience
- Stability Backports for 16.2