Skip to content

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

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/sveltejs-vite-plugin-svelte-7.x
Open

chore(deps): update dependency @sveltejs/vite-plugin-svelte to v7#437
renovate[bot] wants to merge 1 commit intomainfrom
renovate/sveltejs-vite-plugin-svelte-7.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 23, 2026

This PR contains the following updates:

Package Change Age Confidence
@sveltejs/vite-plugin-svelte (source) ^6.2.1^7.0.0 age confidence

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 - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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.

@renovate renovate bot requested review from baxen, matt2e and wesbillman as code owners March 23, 2026 02:30
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: cc8d77c906

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines 861 to +863
peerDependencies:
svelte: ^5.0.0
vite: ^6.3.0 || ^7.0.0
svelte: ^5.46.4
vite: ^8.0.0-beta.7 || ^8.0.0

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Upgrade Vite before pinning vite-plugin-svelte v7

This lockfile update pulls in @sveltejs/vite-plugin-svelte@7.0.0, whose own peer deps now require vite: ^8.0.0-beta.7 || ^8.0.0, but both consumers changed in this commit (apps/differ/package.json and apps/staged/package.json) still pin Vite to ^7.2.4. That leaves both apps on an unsupported dependency set (the lockfile even resolves the plugin against vite@7.3.1), so fresh installs and vite dev/build can break as soon as the plugin exercises a Vite 8-only API. Please upgrade Vite in the same change or keep the plugin on the 6.x line.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants