Next.js 16.3 ships Instant Navigations for SPA-like speed
Next.js 16.3 (Preview) brings SPA-like instant navigations to server-driven apps: Stream or Cache for instant routes, or Block to opt out. It adds Partial Prefetching that fetches one reusable shell per route instead of per link.
On June 24, 2026, Vercel announced Next.js 16.3, released under the @preview tag, featuring Instant Navigations — a direct answer to the long-standing complaint that Server Components can make apps feel unresponsive on navigation.
Key points
- Stream / Cache / Block: when a route
awaits data, you choose Stream with<Suspense>(instant loading state) or Cache with'use cache'(instant cached UI) to make navigation instant; or opt out withexport const instant = falseto Block. - Enabled via flag: requires
cacheComponents: trueinnext.config.ts, slated to become a default in a future major release. - Partial Prefetching: instead of prefetching per link, Next.js now fetches one reusable shell per route and caches it client-side — e.g. 20 chat links prefetch once for the
/chat/[id]route. - Dev tooling: Instant Insights turns slow navigations into dev-time errors; a Navigation Inspector in DevTools and an
instant()Playwright test helper catch regressions. - Note: this is a pre-production release (
npm install next@preview) with known issues, such as Instant Insights tooling on Safari.
Source
Next.js
#Next.js#React#SPA#prefetching#performance
This summary was written by the ORA·tech AI assistant. Read the original for full context.
Related
Frontend & Web Platform
TypeScript 7.0 ships: a Go-native port 8–12x faster
Frontend & Web Platform
What's new in Svelte, July 2026: SvelteKit config in vite.config.js, paving the way to SvelteKit 3
Frontend & Web Platform