SvelteKit 3.0 Ships as a Stable Release

SvelteKit 3.0 has been available on the npm registry since October 1, 2026, after several weeks as a release candidate tracked here on mail-studio.com. The stable release confirms every breaking change flagged during the testing phase: new environment requirements, reorganized internal modules, and the removal of several long-standing APIs. For teams still running SvelteKit 2, the migration window is now open for good.

#A release that closes out the candidate cycle

The release candidate covered here in late August already laid out the essentials: configuration moving into Vite, the $lib alias being replaced, and a higher minimum toolchain. The stable release does not change that trajectory, it locks it in. No additional grace period is planned for the removed APIs.

#What the baseline requirements become

The minimum technical baseline moves on several fronts at once, which makes it worth auditing the full toolchain before starting a migration.

The bump to TypeScript 6 fits a broader pattern across the JavaScript ecosystem, where frameworks increasingly stop guaranteeing compatibility with TypeScript releases older than a year.

#Imports that need fixing in existing code

The $app/stores module is removed entirely, in favor of $app/state, which is built on Svelte 5 runes. The $lib alias, used in nearly every SvelteKit project, is replaced by the #lib subpath export.

- import { page } from '$app/stores';
+ import { page } from '$app/state';

- import Button from '$lib/components/Button.svelte';
+ import Button from '#lib/components/Button.svelte';

#A migration tool to handle most of the work

The Svelte team ships an automated migration command that handles most of the mechanical changes (imports, config, renamed options) without requiring manual edits across every file.

npx sv@next migrate sveltekit-3 --tasks all --confirm

The output still needs a review pass: behavioral changes, such as the cookie path now defaulting to / or the merge of the noScroll and keepFocus options into a single reset parameter, are not always caught by a plain text replacement.

SvelteKit 3.0 closes out a release-candidate cycle that began in late summer, with no further transition step for projects still relying on $app/stores.

#Key takeaways

SvelteKit 3.0 formalizes a modernization that was already announced: configuration centered on Vite, reorganized imports, and a baseline aligned with recent Node, TypeScript, and Vite releases. The sv migrate command handles most of the mechanical work, but a manual review remains necessary for behavioral changes, particularly around navigation and cookies.

Further reading: full SvelteKit release notes on GitHub.