TL;DR
Get monitors, keyboards and dev gear delivered free — and shop member deals
- Fast, free delivery on millions of items
- Access to Prime Big Deal Days deals on October 6–7
- Prime Video, Amazon Music and more included
SvelteKit 3, the latest major version of Svelte’s official application framework, is now available. The release changes configuration and the library alias, among other updates, and includes a migration command that can update code and produce a TODO list. Remote functions remain unfinished and require an experimental flag for now.
SvelteKit 3, the third major version of Svelte’s official application framework, is now available, bringing changes to configuration, imports, environment variables, service workers and error handling. The Svelte team says developers can use the sv migrate command to automate as much of the upgrade as possible, while warning that some migration tasks may still need manual work.
The release post describes SvelteKit 3 as the same framework with added polish, more type safety and less unnecessary code. However, this is a major-version upgrade, and the team says it includes breaking changes. The highlighted change to project setup moves configuration from svelte.config.js into vite.config.ts. The framework’s $lib alias also becomes #lib, which the team says uses standard subpath imports.
Other changes listed by the Svelte team include more capable and easier-to-use environment variables, less boilerplate for service workers, and improvements to error handling. The post does not provide benchmarks or quantify the effects of these changes. Developers can start a new project with npx sv create my-new-app, according to the release instructions.
For existing projects, the recommended migration command is npx sv migrate sveltekit-3 –tasks all –confirm. The team says it will automatically migrate as much of a codebase as it can and generate a TODO list for remaining work. The release post points users to a migration guide for the full set of breaking changes and says a recent release-candidate announcement offers a shorter overview.
How the Upgrade Affects Svelte Teams
The release matters most to teams maintaining existing SvelteKit applications. A major version can affect project configuration and imports, so updating is not necessarily a matter of installing a new package and continuing unchanged. The migration command is intended to reduce repetitive upgrade work, but its generated TODO list signals that developers should review the result and account for any remaining tasks.
The changes also touch regular development and application behavior: configuration now belongs in Vite’s configuration file, library imports use a different alias, and environment-variable and error-handling systems have been revised. These are practical points for maintainers to check when planning an upgrade, even though the supplied release material does not detail every compatibility effect or quantify performance gains.
Remote functions could become a more substantial part of the framework’s future client-server workflow, but they are not ready for ordinary use yet, according to the Svelte team. That distinction matters for developers choosing whether to adopt SvelteKit 3 for current production work: the available release should not be confused with a completed, stable remote-functions feature.
As an affiliate, we earn on qualifying purchases.
What Changes From Earlier SvelteKit
SvelteKit is the official application framework for Svelte. The team characterizes version 3 as familiar to people who have used earlier releases, while listing a set of changes that require attention during an upgrade. The release post frames the update around polish, type safety and removing unnecessary material, but it does not give a detailed technical comparison of version 2 and version 3.
The team’s migration guidance is part of the announcement: run the migration command with the listed options, then work through the generated TODO list and consult the migration guide for the complete breaking-change information. New projects can be created with the sv create command. The release post also says remote functions depend on Async Svelte, which currently requires an experimental flag; that makes them a developing feature rather than a finished part of the release’s standard offering.
The announcement also mentions an upcoming in-person Svelte Summit in Ljubljana, Slovenia, scheduled for November 19–20 and described as a celebration of Svelte’s 10th birthday. The supplied source does not state the year for those dates, so the event timing cannot be matched to a calendar year from this material alone.
As an affiliate, we earn on qualifying purchases.
Migration Work and Remote Functions
The release material does not specify how many projects the migration command can update without manual intervention, or which cases are most likely to produce TODO items. It also does not list every breaking change in the announcement itself; developers need the linked migration guide for those details. The command’s promise to migrate as much as possible is the team’s description of its tool, not a guarantee that every codebase will upgrade cleanly.
The status and release timetable for remote functions remain open. The Svelte team says they are not ready and that using them currently requires an experimental flag through Async Svelte, but the supplied material gives no target date for their general availability. The announcement also does not provide a publication date, making the timing of the release and the year of the November summit dates unclear from the source provided.
As an affiliate, we earn on qualifying purchases.
Upgrade Steps and Feature Follow-Up
Teams considering an upgrade can run npx sv migrate sveltekit-3 –tasks all –confirm, review the changes and generated TODO list, and use the migration guide to check for breaking changes that need attention. Developers starting new applications can use npx sv create with a project name. The release announcement does not give a support schedule or a deadline for moving from an earlier version.
For remote functions, the next milestone is not specified. The Svelte team says work on them remains a priority, but developers should treat the feature as experimental until the team announces a change in status. The announcement also points readers to the Svelte Summit scheduled for November 19–20 in Ljubljana, though the source does not identify the year.
JavaScript environment variable manager
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
Is SvelteKit 3 available now?
Yes. The Svelte team’s release post says SvelteKit 3 is now available.
How can an existing project migrate to SvelteKit 3?
The announcement recommends running npx sv migrate sveltekit-3 –tasks all –confirm. The command is intended to automate as much of the migration as possible and produce a TODO list for remaining work.
What are the main breaking changes?
The highlights include moving configuration from svelte.config.js to vite.config.ts and changing the $lib alias to #lib. The team also lists changes to environment variables, service workers and error handling, and directs developers to its migration guide for the full details.
Are remote functions ready for general use?
No. The Svelte team says they are not ready yet. Using them currently requires Async Svelte and an experimental flag; the announcement gives no general-availability date.
Source: hn
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
