Update dependency @sveltejs/vite-plugin-svelte to v7

[renovate]

This PR contains the following updates:

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

---

Release Notes

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

v7.3.0

Compare Source

Minor Changes

• feat: pass environment to dynamicCompileOptions (#​1386)

Patch Changes

• fix: don't log inline config when encountering unexpected options (#​1376)

v7.2.0

Compare Source

Minor Changes

• feat(inspector): add a context menu with current component stack (#​1370)

v7.1.4

Compare Source

Patch Changes

• fix: enforce ltr styles for inspector (#​1324)

v7.1.3

Compare Source

Patch Changes

• fix: ensure the inspector is injected into the client correctly for Vite+ projects (#​1355)

v7.1.2

Compare Source

Patch Changes

• fix: correctly resolve compiled CSS on the server for dependencies with Svelte files (#​1342)

v7.1.1

Compare Source

Patch Changes

• fix: pass typescript.onlyRemoveTypeImports to transformWithOxc in vitePreprocess so that value imports are not dropped when they are only referenced in Svelte template markup (#​1326)

• fix: correctly resolve compiled CSS for optimised Svelte dependencies on the server (#​1336)

v7.1.0

Compare Source

Minor Changes

• feat: enable optimizer for server environments during dev (#​1328)

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: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ 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.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: frontend/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: tsflow-frontend@0.0.1
npm error Found: vite@7.3.6
npm error node_modules/vite
npm error   dev vite@"^7.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vite@"^8.0.0-beta.7 || ^8.0.0" from @sveltejs/vite-plugin-svelte@7.3.0
npm error node_modules/@sveltejs/vite-plugin-svelte
npm error   dev @sveltejs/vite-plugin-svelte@"^7.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-09-03T10_57_44_028Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-03T10_57_44_028Z-debug-0.log