SvelteKit release notes, breaking changes, and upgrade notes.
Web development, streamlined StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
This prerelease version of SvelteKit introduces breaking changes by moving several types and functions to new locations. It also includes several bug fixes related to Vite plugin hooks and prerendering.
affected
Developers using `RequestEvent`, `Cookies`, remote function types, or `isValidationError` in their SvelteKit projects are affected by the breaking changes.
action
Update imports to use the new locations for the moved types and functions.
release_signals
-Remote function types and `isValidationError` moved to `@sveltejs/kit/remote`
-`RequestEvent` and `Cookies` moved to `$app/server`
This release introduces several breaking changes, including the relocation of types to new modules and the removal of the `#lib` definition from `paths`. It also includes minor improvements like better response logging and various dependency updates.
affected
Developers using SvelteKit will need to update their code to accommodate the breaking changes, particularly those related to type locations and module extensions.
action
Review the breaking changes and update your codebase accordingly.
release_signals
-Move remote function types to `$app/server`
-Remove `#lib` definition from `paths`; requires explicit module extensions
This release introduces several breaking changes, primarily involving the relocation of various types and functions to new modules. Additionally, it includes minor features and bug fixes.
affected
Developers using the relocated types and functions will need to update their imports and handle errors differently.
action
Update your code to import the relocated types and functions from their new modules and ensure errors are handled through the `handleError` hook.
release_signals
-Move `defineParams` and associated types to `@sveltejs/kit/params`
This release introduces breaking changes requiring Node 22 or newer, adds warnings for server-only module usage, and improves import alias handling. It also includes various dependency removals and fixes for Windows compatibility and TypeScript configuration.
affected
Users must upgrade to Node 22 or newer to use this version.
action
Upgrade Node.js to version 22 or newer.
release_signals
-Require Node 22 or newer
+Warn when using a `.server.` file or file inside a `server` directory without importing a server-only module
+Transform import aliases into relative imports in files
This release introduces numerous breaking changes, including requiring TypeScript 6 and Node 22.17, and updates to cookie handling. New features include support for hyphens in param names and the addition of the `$app/manifest` module.
affected
Developers using SvelteKit will need to update their code to accommodate numerous breaking changes, including TypeScript 6 requirement, Node 22.17 requirement, and changes to cookie handling.
action
Review the breaking changes and update your codebase accordingly, ensuring all dependencies meet the new requirements.
This release introduces significant breaking changes, requiring Node 22 or newer and Vite 8 with stable rolldown 1.0.0. It also updates dependencies and documentation.
affected
Users must upgrade to Node 22 and Vite 8 to use this version.
action
Upgrade Node to version 22 and Vite to version 8.0.12 or newer.
release_signals
-Require Node 22 or newer
-Require `vite@^8.0.12`, the first Vite 8 release bundling stable `rolldown` 1.0.0
This release introduces breaking changes for edge functions and Node 20 runtimes, requiring Vite 8.0.12 and changing the build target to `es2022`. It also switches to `rolldown` for edge function bundling.
affected
Users of edge functions and Node 20 runtimes are affected by breaking changes.
action
Update to `vite@^8.0.12` and adjust edge function configurations to target `es2022`.
release_signals
-Edge function build target changed to `es2022`
-Requires `vite@^8.0.12` for stable `rolldown` 1.0.0 support
This release introduces several breaking changes, including updates to route handling and Node.js version requirements, along with new features for file compression and route type definitions.
affected
Developers using SvelteKit will need to update their code to accommodate breaking changes, especially around route handling and Node.js version requirements.
action
Update your SvelteKit project to handle the breaking changes and take advantage of new features.
release_signals
-Refresh all load functions/queries when clicking a link to the current URL.
-Only include routes with a `+page` or `+server` in `RouteId`.
Move `Page`, `ReadonlyURL`, and `ReadonlyURLSearchParams` from `@sveltejs/kit` to `$app/state`
-Move `BeforeNavigate`, `OnNavigate`, `AfterNavigate`, `Navigation`, `NavigationTarget`, `NavigationType`, `GotoOptions`, and the `Navigation*` variant types from `@sveltejs/kit` to `$app/navigation`
-Move `ActionResult` and `SubmitFunction` from `@sveltejs/kit` to `$app/forms`
-Remove `handleValidationError` and pass remote function validation errors to `handleError` with `kind: 'validation'`
+Ignore files with + prefix if they contain test/spec/stories