SvelteKit 3 is out. The official framework for building apps with Svelte gets a major update, and the team wants you to know it mostly works the same way it always did — except with better types, fewer rough edges, and a cleaner setup process.
The headline: SvelteKit 3 is here. Get it while it’s hot.
The Migration Command
If you have an older SvelteKit app, the upgrade path starts with a single command:
sh
npx sv migrate sveltekit-3 --tasks all --confirm
That line does the heavy lifting. It migrates as much of your existing code as possible, then spits out a TODO list for anything it couldn’t handle automatically. The source notes that robots will make quick work of the remaining tasks if you lean on automation.
The command is the practical heart of the announcement. It’s a promise that upgrading doesn’t have to be a full rewrite, and it backs that promise with an actual tool.
Creating a New App
For fresh projects, the command is simpler:
sh
npx sv create my-new-app
That sets up a new SvelteKit 3 app from scratch, using the latest defaults and configurations.
What Changed Under the Hood
The release brings several structural shifts. The biggest is where configuration lives:
- Configuration now sits in
vite.config.tsinstead ofsvelte.config.js - The
$libalias is gone, replaced by the standard subpath import syntax (#lib) - Environment variables are more powerful and easier to use
- Service workers need less boilerplate
- Error handling is improved across the board
These changes are small individually, but together they move SvelteKit toward a more standard workflow. The alias change replaces a custom syntax with one that follows the language’s conventions.
Remote Functions Are Coming
Remote functions are not quite ready. They are the top priority, and they are described as “a set of utilities for secure, efficient, type-safe client-server communication.”
“a set of utilities for secure, efficient, type-safe client-server communication”
They note that similar ideas exist elsewhere, but they believe this implementation will stand out. Using them currently requires Async Svelte, which for now needs an experimental flag.
The team is explicit about the timing: they are not hiding the fact that this feature is unfinished. They are putting it front and center as the project’s main focus.
The Breaking Changes
Any major version bump comes with trade-offs, and SvelteKit 3 is no exception. The migration guide covers the full list of changes, though the announcement offers a quick rundown of the notable ones above.
The shift to vite.config.ts means existing build scripts will break unless they are updated. The alias change means any code depending on $lib will need rewriting. The error handling improvements are broadly positive, but they could require updates to custom error-handling logic.
The announcement frames these as minor friction rather than a major overhaul. That’s a fair reading of the facts, but it also means users should expect some manual work during the upgrade.
The Cake in Ljubljana
The announcement closes with a reminder about the next in-person Svelte Summit. It runs November 19-20 in Ljubljana, Slovenia, and it marks a milestone: Svelte’s 10th birthday.
The team says they’d love to share some cake with attendees. It’s a small detail, but it lands as genuine — a reminder that the project has been around for a decade, and the people running it still seem to care about the community.
Why This Matters
The release shows a project that is maturing without losing its identity. SvelteKit 3 keeps the core Svelte experience intact while tightening up its foundations. The migration command exists to protect existing users, and the new features are being rolled out in a controlled way.
The remote functions work is particularly interesting. The team is putting significant effort into client-server communication, and they want to get it right. The fact that it is not done yet is a sign of ambition, not trouble.
Our Take
SvelteKit 3 is a solid update. The migration tool makes upgrading manageable, the new configuration format moves the project toward standard practices, and the remote functions promise looks promising.
The release is not a radical rethinking of Svelte’s approach. It is a refinement — better types, fewer rough edges, and a clearer path forward. That is exactly what a mature framework should deliver.
For developers who have been waiting for a reason to upgrade, SvelteKit 3 provides one. The migration path exists, the breaking changes are documented, and the new features are worth the effort.
SvelteKit 3 is live. The cake is reserved for November.
Source material: “SvelteKit 3,” svelte.dev.
Get the Notebook.
The day's best stories and every fresh verdict, in plain English, in your inbox by seven. One email a day, no more.