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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sveltejs/vite-plugin-svelte (source)	^3.0.1 -> ^4.0.0

---

Release Notes

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

v4.0.0

Compare Source

Major Changes

• only prebundle files with default filenames (.svelte for components, .svelte.(js|ts) for modules) (#​901)

• remove support for Svelte 4 (#​892)

• breaking(types): some types that have been unintentionally public are now private (#​934)

• disable script preprocessing in vitePreprocess() by default because Svelte 5 supports lang=ts out of the box (#​892)

• replaced svelte-hmr with Svelte 5 compiler hmr integration (#​892)

Minor Changes

• allow infix notation for svelte modules (#​901)

  Previously, only suffix notation .svelte.js was allowed, now you can also use .svelte.test.js or .svelte.stories.js.
  This helps when writing testcases or other auxillary code where you may want to use runes too.

• feat(config): dynamically extract list of svelte exports from peer dependency so that new exports work automatically" (#​941)

• feat(warnings): change default loglevel of warnings originating from files in node_modules to debug. To see them call DEBUG:vite-plugin-svelte:node-modules-onwarn pnpm build. (#​989)

Patch Changes

• fix: make defaultHandler a required argument for onwarn in plugin options (#​895)

• prebundle with dev: true by default (#​901)

• fix(dev): compile with hmr: false for prebundled deps as hmr does not work with that (#​950)

• fix: ensure svelte modules correctly run in DEV mode (#​906)

• ensure consistent use of compileOptions.hmr also for prebundling (#​956)

• fix(optimizeDeps): avoid to optimise server only entrypoints of svelte that are never used on the client (#​941)

• update peer on workspace packages to avoid packages bumping each other (#​916)

• export PluginOptions interface (#​976)

• Remove log about experimental status of Svelte 5. Note that breaking changes can still occur while vite-plugin-svelte 4 is in prerelease mode (#​894)

• fix: ensure vite config is only resolved once during lazy init of vitePreprocess (#​912)

• fix(vitePreprocess): default to build config so that svelte-check does not trigger dev-only plugins (#​931)

• fix: only apply infix filter to basename (#​920)

• fix: disable hmr when vite config server.hmr is false (#​913)

• fix(dev): make sure custom cssHash is applied consistently even for prebundled components to avoid hash mismatches during hydration (#​950)

• Updated dependencies [22baa25, 49324db, e9f048c, 213fedd]:

  • @​sveltejs/vite-plugin-svelte-inspector@​3.0.0

v3.1.2

Compare Source

Patch Changes

• add warning for svelte5 users to update to vite-plugin-svelte@4 (#​964)

v3.1.1

Compare Source

Patch Changes

• fix: ensure vite config is only resolved once during lazy init of vitePreprocess (#​917)

• fix: disable hmr when vite config server.hmr is false (#​917)

---

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.

[changeset-bot]

⚠️ No Changeset found

Latest commit: f8b09df

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

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 4.x releases. But if you manually upgrade to 4.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.