chore(deps): update dependency @sveltejs/vite-plugin-svelte to v7 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@sveltejs/vite-plugin-svelte (source)	^6.2.4 → ^7.0.0

---

Release Notes

sveltejs/vite-plugin-svelte (@​sveltejs/vite-plugin-svelte)

v7.0.0

Compare Source

Major Changes

• breaking(deps): require vite 8 (#​1266)

• breaking(options): remove deprecated options (#​1274)

  • vitePlugin.hot in svelte.config.js
    use compilerOptions.hmr instead
  • vitePlugin.ignorePluginPreprocessors in svelte.config.js
    no longer needed
  • api.idFilter of vite-plugin-svelte:api
    use api.filter instead
  • plugin.api.sveltePreprocess of other vite plugins
    Update affected plugins to a newer version or remove them.
    See docs for more information.

• breaking(dev): no longer overrides compilerOptions.cssHash because Svelte now produces a stable css hash by itself (#​1271)

• breaking(inspector): integrate vite-plugin-svelte-inspector into vite-plugin-svelte to avoid circular dependency (#​1270)

• breaking(deps): require svelte 5.46.4 or later (#​1271)

Patch Changes

• chore: upgrade vitefu to compatible peer dependency range (#​1286)

• remove author field from package.json (#​1281)

---

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
sv-router	Ignored	Preview	Feb 23, 2026 9:42pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 10fa8fc

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.

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