SvelteKit query composition and Next.js prefetch stability
June 8–14, 2026
SvelteKit 2.65.0 and 3.0.0-next shipped a system for queries to refresh other queries, while Next.js stabilized its prefetch API and enabled Turbopack's filesystem cache by default in canary and preview releases.
Queries that talk to each other
SvelteKit 2.65.0 — and the corresponding 3.0.0-next.3 — introduced the ability for queries to refresh other queries, a building block that lets one data dependency cascade updates across the page without manual invalidation wiring. The stable release also deduplicates remote data and skips the client build entirely when every route has CSR disabled. The next branch picks up the same query-refresh feature plus a fix to use SSE for query.live in 3.0.0-next.2. A subsequent 2.65.1 patch avoids importing Vite's dev client code into builds with a non-standard NODE_ENV and cleans up unused bundle artifacts when using bundleStrategy: 'inline'.
Next.js: prefetch API stable, cache enabled by default
The biggest cluster of changes this week came from the Next.js canary and preview tracks, which together stabilized several APIs that had been experimental since the early days of v16. In canary 47 the unstable_ prefix was dropped from the instant API, catchError, and retry — these are now first-class exports. Separately, export const prefetch graduated from unstable to stable, and the force-runtime prefetch option was renamed to allow-runtime. The preview.0 and preview.3 releases bundle those same stabilizations with Turbopack's filesystem cache for builds enabled by default in non-stable releases.
Canary 46 eliminated the experimental.useNodeStreams flag (now always on) and removed dead web streams code for cache components. Canary 48 turned on the cold cache dev indicator and fixed staging of short-lived 'use cache' entries. Canary 49 warns when prefetch={true} navigation is used without Partial Prefetching enabled. Canary 50 allows root parameters in the App Shell client. And canary 51 avoids a premature Suspense fallback flash in the streaming dev render — a quality-of-life fix for anyone who's watched the UI flicker during development.
Outside the canary track, two mechanical releases — 16.2.8 and 16.2.9 — corrected the npm latest tag, which had been incorrectly pointing at a prerelease version, a side effect of the move to Trusted Publishing.
Other notes
Nuxt shipped hotfixes 4.4.8 and 3.21.8 to address a macOS dev server startup failure caused by overly long Unix socket names. Expo Orbit's 2.7.0 added support for DeviceHub.app on Xcode 27 and fixed several emulator-related bugs. And the htmx project published a new essay, The University In The AI Era, reflecting on what AI means for computer science education.
Releases covered
- Next.js v16.3.0-canary.47 stabilizes instant, catchError, and retry APIs
- Next.js v16.3.0-preview.0 stabilizes export const prefetch and renames prefetch option
- Next.js v16.3.0-preview.3 enables turbopack filesystem cache by default
- Next.js v16.3.0-canary.48 enables turbopack cache by default and adds cold cache indicator
- Next.js v16.3.0-canary.49 warns on prefetch={true} navigation
- Next.js v16.3.0-canary.50 allows root params in App Shell (client)
- Next.js v16.3.0-canary.51 avoids premature Suspense fallback flash
- Next.js v16.2.8 fixes latest tag pointing to prerelease
- Next.js v16.2.9 dependency update