SvelteKit 3
- ID
- 31089
- Status
- summarized
- Published
- 02 Oct 2026, 4:14 AM
- Fetched
- 02 Oct 2026, 7:33 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://svelte.dev/blog/sveltekit-3-is-here
- Source URL
- https://hnrss.org/best
Summary
- Score
- 7.0
- Created
- 02 Oct 2026, 7:34 PM
- Tags
- Audience
- developersvibe_coders
What happened
SvelteKit 3.0 shipped on October 1, 2026, and the team describes it as the same framework with more polish and type safety. Breaking changes include moving configuration from svelte.config.js into vite.config.ts, renaming the $lib alias to #lib via standard subpath imports, plus reworked environment variables, less service-worker boilerplate, and improved error handling. Remote functions — type-safe client-server utilities — are explicitly not ready and still need Async Svelte behind an experimental flag, though the team calls them their top priority.
Why it matters
If you maintain a SvelteKit app, the $lib to #lib rename and the config move to vite.config.ts will break imports and build setup, so run `npx sv migrate sveltekit-3 --tasks all --confirm` and expect it to leave a TODO list rather than finish the job. If you were planning to build a data layer around remote functions, don't wait — they still require an experimental Async Svelte flag, so design for the current load/action patterns instead.
Discussion angle
The release leans on 'your robot friends will make short work of it' for the migration — worth testing live whether an AI coding agent can actually complete the $lib to #lib and svelte.config.js to vite.config.ts changes on a real project, and what it silently gets wrong.