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

[renovate]

This PR contains the following updates:

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

---

Release Notes

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

v6.0.0

Compare Source

Major Changes

• drop support for node18 and update exports map to use default export. cjs is supported via require esm in node 20.19+ (#​1129)

• Remove experimental "advanced raw queries" feature. Basic File.svelte?raw is still supported. (#​1145)

• Using the typescript preprocessor now requires a tsconfig.json with verbatimModuleSyntax enabled, eg @​tsconfig/svelte (#​1135)

• remove support for loading commonjs svelte config files (#​1142)

• bump vite peer dependency to ^6.3.0 || ^7.0.0 (#​1130)

• define filters using object hook syntax and optimize the filter for resolveId (#​1132)

  NOTE
  include logic has changed to files matching svelteConfig.include OR svelteConfig.extensions. Previously only files matching both were loaded and transformed.

• split preprocess and compile into separate plugins (#​1145)

  It allows vite plugins to transform code between preprocess and compile, see docs and is the recommended way to replace plugin.api.sveltePreprocess usage in other vite plugins.
  You can also use vite-plugin-inspect now to inspect the result of svelte.preprocess by checking the transform of vite-plugin-svelte:preprocess

  NOTE
  This can be a breaking change in case you have other plugins besides vite-plugin-svelte transforming your svelte code
  To fix this, read the docs on how to order plugins in relation to preprocess and compile

Minor Changes

• Add experimental support for rolldown-vite (#​1135)

• replace esbuild optimizer with rolldown optimizer if rolldown-vite is used (#​1135)

• add support for loading TypeScript Svelte config files in runtimes that support it (#​1142)

  NOTE
  This change only applies to vite-plugin-svelte.

  To use svelte.config.ts in SvelteKit, with the Svelte VS Code extension or other tools reading the Svelte config file, you have to wait until support is implemented there.

Patch Changes

• reduce deprecation logging to info and allow disabling it with a flag (#​1158)

• refactor internal caching to reduce code, memory use and avoid perEnvironmentCache (#​1154)

• fix: crawl local workspace private packages devDependencies for generating vite config ssr.noExternal (#​1155)

• log known-issues link when using rolldown-vite (#​1144)

• use vite environment api internally (#​1145)

• remove vite7 beta releases from peerDependency range. (#​1151)

• deprecate plugin.api.sveltePreprocess (#​1145)

---

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.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
svelte-changelog	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 10, 2025 7:36pm