Prefetch is now stable in Next.js, force-runtime becomes allow-runtime, and Stream Cache Components skip restarts on cache miss—three changes that tighten the build pipeline.
Summary
Stabilizing prefetch reduces API churn for developers optimizing navigation. Renaming force-runtime to allow-runtime clarifies intent. Cache miss handling in Stream Components eliminates unnecessary dev-mode restarts, speeding local iteration.
Why it matters
Stabilizing prefetch reduces API churn for developers optimizing navigation. Renaming force-runtime to allow-runtime clarifies intent. Cache miss handling in Stream Components eliminates unnecessary dev-mode restarts, speeding local iteration.
Implementation verdict
Straightforward adoption: update prefetch imports, rename runtime config keys if you use them. The cache miss fix is automatic in the next release. Worth upgrading immediately if you rely on prefetch patterns or frequent cache invalidation in development.
Sources
Dev Signal
Get briefs like this in your inbox — free, every weekday.
100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.