●Change8

Migrating to SvelteKit @sveltejs/kit@3.0.0-next.7

Version @sveltejs/kit@3.0.0-next.7 introduces 5 breaking changes. This guide details how to update your code.

Released: 7/8/2026

5
Breaking Changes
3
Migration Steps
7
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

form.error$app/stores*.remote.ts/jsparams.js/tsquery.refresh()$app/env/*node:async_hooks

Breaking Changes

●Issue #1

The type of `form.error` has changed from `any` to `App.Error | undefined`.

●Issue #2

Tracing functionality has been moved out of the experimental namespace, and the `instrumentation` flag has been removed.

●Issue #3

The `$app/stores` module has been removed. Consumers must find alternatives for the functionality previously provided here.

●Issue #4

The use of `*.remote.ts/js` files is now disallowed unless `experimental.remoteFunctions` is explicitly enabled.

●Issue #5

Param files in folders (e.g., `+page.params.js`) are removed in favor of using the `params.js/ts` file within the directory.

Migration Steps

  1. 1
    If you relied on `$app/stores`, migrate to the new mechanism for accessing those values.
  2. 2
    If you were using `*.remote.ts/js` files, either rename them or enable `experimental.remoteFunctions` in your configuration.
  3. 3
    Replace param files in folders (e.g., `src/routes/foo/[param]/+page.params.js`) with a single `params.js/ts` file in the corresponding directory (e.g., `src/routes/foo/[param]/params.js`).

Release Summary

This release introduces major breaking changes, including the removal of `$app/stores` and changes to parameter file conventions, alongside several bug fixes for server execution and build processes.

Need More Details?

View the full release notes and all changes for SvelteKit @sveltejs/kit@3.0.0-next.7.

View Full Changelog