--- collection: frontend-frameworks collection_name: Frontend Frameworks week_start: 2026-06-01 title: SvelteKit 3 goes alpha with bundler shifts and tougher requirements release_count: 31 generated: 2026-07-11 canonical: https://releases.sh/collections/frontend-frameworks/digest/2026-06-01 --- # SvelteKit 3 goes alpha with bundler shifts and tougher requirements SvelteKit’s first 3.0 alpha drops alongside major adapter rewrites that migrate from Rollup to Rolldown, while Nuxt ships emergency security patches across both its v3 and v4 lines. ### SvelteKit 3: the path forward This week SvelteKit took a big step toward its next major version with the release of [@sveltejs/kit@3.0.0-next.0](/release/rel_-4D3xOWG2HRorYYTuP0tG-sveltejs-kit-3-0-0-next-0) and an accompanying suite of adapter pre-releases. The core framework bumps minimum requirements to Node 22 and TypeScript 6, upgrades to cookie v1 (which restricts cookie names to ASCII characters), and removes the `preloadStrategy` option in favor of always using `modulepreload`. A follow-up [3.0.0-next.1](/release/rel_X2PjTEUYPHCyKmhHMOcPW-sveltejs-kit-3-0-0-next-1) patch restores the `$app/environment` alias for compatibility with dependencies that still import from the old path. Perhaps more consequential than the framework changes themselves are the shifts happening in the adapter layer. [@sveltejs/adapter-node@6.0.0-next.0](/release/rel_gNWYNl6z97D0ypcAhbFRC-sveltejs-adapter-node-6-0-0-next-0) and [@sveltejs/adapter-vercel@7.0.0-next.0](/release/rel_1uAARSakxN46Z_WbsruQd-sveltejs-adapter-vercel-7-0-0-next-0) both swap Rollup for Rolldown as their bundler, with the Vercel adapter targeting `es2022` for edge functions. [@sveltejs/adapter-netlify@7.0.0-next.0](/release/rel_xB_YtkWSDZAqc0BEFLwuz-sveltejs-adapter-netlify-7-0-0-next-0) additionally aligns with the stable Netlify Frameworks API, meaning deployments now require Netlify CLI v17.31.0 or later. [@sveltejs/adapter-cloudflare@8.0.0-next.0](/release/rel_GlQqUbPRJ0zoHTyGn-5jc-sveltejs-adapter-cloudflare-8-0-0-next-0) upgrades `@cloudflare/workers-types` and replaces `platform.context` with `platform.ctx`. Meanwhile, [@sveltejs/package@3.0.0-next.0](/release/rel_xbkAMGlQmEps4vaOr5Z9o-sveltejs-package-3-0-0-next-0) and [@sveltejs/enhanced-img@1.0.0-next.0](/release/rel_2f0HbiPNi9nyelvi_19Ta-sveltejs-enhanced-img-1-0-0-next-0) also require Node 22, with enhanced-img additionally mandating Vite 8 and `vite-plugin-svelte` 7. For users not ready to jump to v3, the 2.x line continues to improve. [@sveltejs/kit@2.63.0](/release/rel_IKRBGI6fysMCdUUajSKUz-sveltejs-kit-2-63-0) adds explicit environment variable support, and [@sveltejs/kit@2.63.1](/release/rel_jatpqtXpQS7Hz1DiuV6hx-sveltejs-kit-2-63-1) fixes a Windows path issue in generated `env.d.ts` imports and switches `query.live` to SSE. The [@sveltejs/kit@2.62.0](/release/rel_QC0D3efEQWQbom1jcflJ4-sveltejs-kit-2-62-0) release from earlier in the week lets you pass SvelteKit config through the Vite plugin, preserves multiple `Set-Cookie` headers on 304 responses, and catches streaming errors in load functions on the client. ### Svelte core: quiet stability The Svelte compiler itself saw three patch releases. [svelte@5.56.1](/release/rel_TmR1ObxsJocsvTQ-0Tff_-svelte-5-56-1) adds compile-time errors for duplicate declaration tags and fixes cross-referencing between declarators. [svelte@5.56.2](/release/rel_xpePsHLEr4QLCMmP5fBdm-svelte-5-56-2) improves tracking of effect end nodes for async sibling components and quiets a false-positive reactivity loss warning. [svelte@5.56.3](/release/rel_f_oYlAfc5R5lBkpkleWCK-svelte-5-56-3) ignores errors in destroyed effects and types BigInts in `$state.snapshot()` returns. ### Nuxt security hotfixes Both Nuxt v3 and v4 received urgent security releases on the same day. [Nuxt v4.4.7](/release/rel_a4lDFFCTA_XgU-KAxN_RL-v4-4-7) and [Nuxt v3.21.7](/release/rel_bCTjUtJJOwjnBdeUBdiF3-v3-21-7) fix a `noSSR` assignment ordering issue in Nitro that could affect payload extraction, and patch a Vite `allowDirs` filtering bug where directories with shared prefixes could be incorrectly excluded. Users on either version should upgrade promptly. ### Next.js backports and Turbopack progress Next.js spread fixes across three release channels. The [v16.2.7](/release/rel_uF78CfsWgCtTv-rHtVNbI-next-js-v16-2-7-fixes-hydration-router-query-and-server-action-forwarding) backport resolves a dev mode hydration failure from HTTP cache, `router.query` corruption with basePath and rewrites, server action forwarding loops with middleware rewrites, and FormData entry dropping — the latter also backported to [v15.5.19](/release/rel_wYzGs3YAhrIdYpTvW6Sk5-next-js-v15-5-19-fixes-formdata-entry-loss). On canary, Turbopack work continues with [effect eviction and memory management](/release/rel_nHMHZi-Domrtry_gRtxom-next-js-v16-3-0-canary-44-enables-turbopack-effect-eviction-and-memory), and [improved NFT tracing](/release/rel_DsyT2Q9nWLiOCw2uOsVlk-next-js-v16-3-0-canary-37-awaits-instrumentation-in-routemodule-and-refactors). ## Releases covered ### Nuxt - [v4.4.7](https://releases.sh/release/rel_a4lDFFCTA_XgU-KAxN_RL-v4-4-7) - [v3.21.7](https://releases.sh/release/rel_bCTjUtJJOwjnBdeUBdiF3-v3-21-7) ### Svelte - [@sveltejs/kit@3.0.0-next.0](https://releases.sh/release/rel_-4D3xOWG2HRorYYTuP0tG-sveltejs-kit-3-0-0-next-0) - [@sveltejs/kit@3.0.0-next.1](https://releases.sh/release/rel_X2PjTEUYPHCyKmhHMOcPW-sveltejs-kit-3-0-0-next-1) - [@sveltejs/adapter-node@6.0.0-next.0](https://releases.sh/release/rel_gNWYNl6z97D0ypcAhbFRC-sveltejs-adapter-node-6-0-0-next-0) - [@sveltejs/adapter-vercel@7.0.0-next.0](https://releases.sh/release/rel_1uAARSakxN46Z_WbsruQd-sveltejs-adapter-vercel-7-0-0-next-0) - [@sveltejs/adapter-netlify@7.0.0-next.0](https://releases.sh/release/rel_xB_YtkWSDZAqc0BEFLwuz-sveltejs-adapter-netlify-7-0-0-next-0) - [@sveltejs/adapter-cloudflare@8.0.0-next.0](https://releases.sh/release/rel_GlQqUbPRJ0zoHTyGn-5jc-sveltejs-adapter-cloudflare-8-0-0-next-0) - [@sveltejs/package@3.0.0-next.0](https://releases.sh/release/rel_xbkAMGlQmEps4vaOr5Z9o-sveltejs-package-3-0-0-next-0) - [@sveltejs/enhanced-img@1.0.0-next.0](https://releases.sh/release/rel_2f0HbiPNi9nyelvi_19Ta-sveltejs-enhanced-img-1-0-0-next-0) - [@sveltejs/kit@2.63.0](https://releases.sh/release/rel_IKRBGI6fysMCdUUajSKUz-sveltejs-kit-2-63-0) - [@sveltejs/kit@2.63.1](https://releases.sh/release/rel_jatpqtXpQS7Hz1DiuV6hx-sveltejs-kit-2-63-1) - [@sveltejs/kit@2.62.0](https://releases.sh/release/rel_QC0D3efEQWQbom1jcflJ4-sveltejs-kit-2-62-0) - [svelte@5.56.1](https://releases.sh/release/rel_TmR1ObxsJocsvTQ-0Tff_-svelte-5-56-1) - [svelte@5.56.2](https://releases.sh/release/rel_xpePsHLEr4QLCMmP5fBdm-svelte-5-56-2) - [svelte@5.56.3](https://releases.sh/release/rel_f_oYlAfc5R5lBkpkleWCK-svelte-5-56-3) ### Vercel - [Next.js v16.2.7 fixes hydration, router.query, and server action forwarding](https://releases.sh/release/rel_uF78CfsWgCtTv-rHtVNbI-dev-mode-hydration-fixed-router-query-corruption-resolved) - [Next.js v15.5.19 fixes FormData entry loss](https://releases.sh/release/rel_wYzGs3YAhrIdYpTvW6Sk5-formdata-entries-no-longer-dropped) - [Next.js v16.3.0-canary.44 enables Turbopack effect eviction and memory management improvements](https://releases.sh/release/rel_nHMHZi-Domrtry_gRtxom-turbopack-effect-eviction-enabled-memory-management-refined) - [Next.js v16.3.0-canary.37 awaits instrumentation in RouteModule and refactors Turbopack NFT](https://releases.sh/release/rel_DsyT2Q9nWLiOCw2uOsVlk-instrumentation-now-awaited-in-routemodule-turbopack-nft-refactored)