SvelteKit 3 arrives with a cleaner config and a one-command migration
SvelteKit 3 Is Here
SvelteKit 3.0 is out. The framework moves configuration into vite.config.ts, swaps the $lib alias for standard subpath imports under #lib, and improves environment variables, service workers, and error handling. A new sv migrate command automates most of the upgrade and generates a TODO list for the rest. Remote functions, the team's top priority, still need an experimental Async Svelte flag.
If you’re agentically inclined, your robot friends will make short work of it.
- pelagicAustral
Svelte is that kind of project that never ceases to reinvent the wheel... they started with a circle, perfect and functional. Then they decided to go with a square, then an octagon, then a hexadecagon... in a few more versions they will eventually get close to something you can put on a cart and drive around.
- poetril
After far too many hours using react, Svelte has become my favorite frontend framework. I’m seeing a lot of comments about how it stacks up in the LLM age. Prior to Opus 4.6-8 (and that era of model releases) they often struggled to get Svelte 4/5 code straight and mixed it up quite a bit.
But having used it A LOT this year for personal projects, large work initiatives, and one-off web tools. I’m happy to say all the modern llms seem to do just fine with it. They even handle the experimental features, like remote functions, very well. It’s mostly preference but I find reading Svelte code much more pleasant than React/Vue.
- jamies
Such a great project. I converted my React-enjoying cofounders to Svelte/SvelteKit worried they wouldn't like it, but they absolutely love it!
We use Svelte extensively at Orb.net for our website (duh), but also as a framework for our desktop and mobile apps. Wails serves our golang and SvelteKit/Svelte provide the UX. It's been tremendous for multiplatform productivity, and binaries are less than 20mb! Nothing like Electron!
- gozzoo
I'm a little out of touch with these technologies (sveltekit, nextjs), but is there any advantage to using the same technology for both frontend and backend development beyond the rise of full-stack developers?
What about using React/Svelte for the frontend and a separate backend in Node.js or another stack? Is there any real advantage to having a single monolithic codebase for everything?
- stillatit
I love the hands-on developer experience of programming in Svelte. But since we're in October of 2026 I have to ask, is the vibe-coding experience in Svelte any different than in React? Can anyone with experience in both comment?
- sensanaty
Are they still sticking to that godawful routing nomenclature of +page.svelte in infinite nested folders?
- killingtime74
The thing I like about Svelte the most is that it's closer to raw HTML. Rather than having to keep up with all the React developments if you're not using it all the time.
- dankobgd
Change for the sake of change without adding anything new, and yes i have used it for years but i kind of don't even like it.