chore(deps): update vite (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@vitejs/plugin-react-swc (source)	^3.11.0 → ^4.0.0
vite (source)	^7.2.7 → ^8.0.0

---

Release Notes

vitejs/vite-plugin-react (@​vitejs/plugin-react-swc)

v4.3.0

Compare Source

Add Vite 8 to peerDependencies range #​1142

This plugin is compatible with Vite 8.

v4.2.3

Compare Source

v4.2.2

Compare Source

Update code to support newer rolldown-vite (#​978)

rolldown-vite will remove optimizeDeps.rollupOptions in favor of optimizeDeps.rolldownOptions soon. This plugin now uses optimizeDeps.rolldownOptions to support newer rolldown-vite. Please update rolldown-vite to the latest version if you are using an older version.

v4.2.1

Compare Source

Fix @vitejs/plugin-react-swc/preamble on build (#​962)

v4.2.0

Compare Source

Add @vitejs/plugin-react-swc/preamble virtual module for SSR HMR (#​890)

SSR applications can now initialize HMR runtime by importing @vitejs/plugin-react-swc/preamble at the top of their client entry instead of manually calling transformIndexHtml. This simplifies SSR setup for applications that don't use the transformIndexHtml API.

Use SWC when useAtYourOwnRisk_mutateSwcOptions is provided (#​951)

Previously, this plugin did not use SWC if plugins were not provided even if useAtYourOwnRisk_mutateSwcOptions was provided. This is now fixed.

v4.1.0

Compare Source

Set SWC cacheRoot options

This is set to {viteCacheDir}/swc and override the default of .swc.

Perf: simplify refresh wrapper generation (#​835)

v4.0.1

Compare Source

Set optimizeDeps.rollupOptions.transform.jsx instead of optimizeDeps.rollupOptions.jsx for rolldown-vite (#​735)

optimizeDeps.rollupOptions.jsx is going to be deprecated in favor of optimizeDeps.rollupOptions.transform.jsx.

v4.0.0

Compare Source

vitejs/vite (vite)

v8.0.0

Compare Source

Features

• update rolldown to 1.0.0-rc.9 (#​21813) (f05be0e)
• warn when vite-tsconfig-paths plugin is detected (#​21781) (ada493e)

Bug Fixes

• deps: update all non-major dependencies (#​21786) (eaa4352)

---

Configuration

📅 Schedule: Branch creation - "before 10am on friday" in timezone Europe/London, 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• 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: modules/api-server/demo-app/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: lovable-tagger@1.1.13
npm error Found: vite@8.0.0
npm error node_modules/vite
npm error   dev vite@"^8.0.0" from the root project
npm error   peer vite@"^4 || ^5 || ^6 || ^7 || ^8" from @vitejs/plugin-react-swc@4.3.0
npm error   node_modules/@vitejs/plugin-react-swc
npm error     dev @vitejs/plugin-react-swc@"^4.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vite@">=5.0.0 <8.0.0" from lovable-tagger@1.1.13
npm error node_modules/lovable-tagger
npm error   dev lovable-tagger@"^1.1.13" from the root project
npm error
npm error Conflicting peer dependency: vite@7.3.1
npm error node_modules/vite
npm error   peer vite@">=5.0.0 <8.0.0" from lovable-tagger@1.1.13
npm error   node_modules/lovable-tagger
npm error     dev lovable-tagger@"^1.1.13" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error 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-03-12T15_26_52_142Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-12T15_26_52_142Z-debug-0.log

[github-actions]

Open in Overmind ↗

---

model|risks_v6
✨Encryption Key State Risk ✨KMS Key Creation

🔥 Risks

Tip

✔ No observations recorded

We weren't able to record any observations for this change. This may indicate limited connectivity between affected items - check that your mapped resources include the expected dependencies.

---

---

💥 Blast Radius

Items 0

Edges 0

[github-actions]

✅ Auto-Approved

---

🟢 Decision

Auto-approved: All safety checks passed

---

🔥 Risks Summary

High 0 · Medium 0 · Low 0

---

View full analysis in Overmind ↗