The line that caught me in this release isn’t a feature. It’s the migration command: one run, it rewrites what it can and leaves a task list for the rest. The Svelte team says outright that an agent will make short work of that list. A task list is exactly the handoff I’d give Claude anyway, so the framework is now writing my prompt for me.
What I’d do: run the migrate on a branch, hand the task list to an agent, read the diff myself. And I wouldn’t plan anything around remote functions yet. They’re the team’s top priority, but they depend on Async Svelte, which still needs an experimental flag.
The story — SvelteKit 3.0, the official application framework for Svelte, is now available. The team calls it the same framework with more polish, more type safety and less junk. An sv migrate command converts as much of a codebase as possible and generates a task list for the rest. Breaking changes include configuration moving to vite.config.ts and the $lib alias becoming #lib. Remote functions are not ready yet. (Source).