chore(deps): update sveltekit (major) - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sveltejs/adapter-auto (source)	^2.1.1 -> ^3.0.0
@sveltejs/kit (source)	^1.30.3 -> ^2.0.3

---

Release Notes

sveltejs/kit (@​sveltejs/adapter-auto)

v3.0.0

Compare Source

Major Changes

• breaking: require SvelteKit 2 (#​11316)

sveltejs/kit (@​sveltejs/kit)

v2.0.3

Compare Source

Patch Changes

• fix: reinstantiate state parameter for goto (#​11342)

v2.0.2

Compare Source

Patch Changes

• fix: prevent endless SPA 404 loop (#​11354)

v2.0.1

Compare Source

Patch Changes

• fix: correctly handle trailing slash redirect when navigating from the root page (#​11357)

v2.0.0

Compare Source

Major Changes

• breaking: remove top-level promise awaiting (#​11176)

• breaking: prevent use of dynamic env vars during prerendering, serve env vars dynamically (#​11277)

• breaking: remove deprecated use:enhance callback values (#​11282)

• breaking: turn error and redirect into commands (#​11165)

• breaking: the type for depends now requires a : as part of the string (#​11201)

• breaking: remove baseUrl fallback from generated tsconfig (#​11294)

• breaking: fail if route with +page and +server is marked prerenderable (#​11256)

• breaking: remove resolvePath in favour of resolveRoute from $app/paths (#​11265)

• breaking: drop support for Svelte 3 (#​11168)

• breaking: require Vite 5.0.3+ (#​11122)

• breaking: generate __data.json files as sibling to .html files (#​11269)

• breaking: fail if +page and +server have mismatched config (#​11256)

• breaking: error if form without multipart/form-data enctype contains a file input (#​11282)

• breaking: require paths pass to preloadCode to be prefixed with basepath (#​11259)

• breaking: @sveltejs/vite-plugin-svelte is now a peer dependency and will need to be installed in each project using SvelteKit (#​11184)

• breaking: stop re-exporting vitePreprocess (#​11297)

• breaking: require path option when setting/deleting/serializing cookies (#​11240)

• breaking: tighten up error handling (#​11289)

• breaking: remove state option from goto in favor of shallow routing (#​11307)

• breaking: disallow external navigation with goto (#​11207)

• breaking: upgrade to TypeScript 5. Default moduleResolution to bundler in user projects to be permissive in consuming and NodeNext when running package to be strict in distributing (#​11160)

• breaking: undefined is no longer a valid value for paths.relative (#​11185)

• breaking: require Node 18.13 or newer (#​11172)

• breaking: fix path resolution (#​11276)

• breaking: remove dangerZone.trackServerFetches (#​11235)

Minor Changes

• feat: add untrack to load (#​11311)

• feat: implement shallow routing (#​11307)

• feat: provide SvelteKit html typings (#​11222)

• feat: redact internal stack trace when reporting config errors (#​11292)

• feat: allow for fine grained invalidation of search params (#​11258)

Patch Changes

• fix: prerender optional parameters as empty when entries contains '*' (#​11178)

• fix: resolve route config correctly (#​11256)

• fix: import Svelte types from svelte/compiler (#​11188)

• fix: reset invalid resources after a successful invalidation (#​11268)

• fix: Adjust fail method and ActionFailure type (#​11260)

• chore(deps): upgrade cookies dependency (#​11189)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[changeset-bot]

⚠️ No Changeset found

Latest commit: f4e8116

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR