chore(deps): update dependency @vitejs/plugin-react to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@vitejs/plugin-react (source)	^5.2.0 → ^6.0.1

---

Release Notes

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

v6.0.1

Compare Source

Expand @rolldown/plugin-babel peer dep range (#​1146)

Expanded @rolldown/plugin-babel peer dep range to include ^0.2.0.

v6.0.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - "before 5am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 has been generated by Mend Renovate using a curated preset maintained by . View repository job log here

[claude]

Claude finished @renovate[bot]'s task in 2m 4s —— View job

---

Review: @vitejs/plugin-react v5 → v6

• Gather context
• Check usages of @vitejs/plugin-react in codebase
• Review v6 breaking changes
• Summarize findings

---

🚨 Critical: Peer Dependency Mismatch (Vite 7 vs Required Vite 8)

@vitejs/plugin-react@6.0.1 declares vite: ^8.0.0 as a required (non-optional) peer dependency, but this project pins vite: ^7.3.1 in pnpm-workspace.yaml:28.

pnpm resolved the package against vite@7.3.1 anyway (visible in pnpm-lock.yaml:13898), silently ignoring the peer constraint. If v6 internally uses Vite 8 APIs that don't exist in Vite 7, this will cause runtime failures. This PR should not be merged until Vite is also upgraded to v8, or until compatibility with Vite 7 is confirmed.

Fix this →

---

⚠️ Potential Issue: babel option without @rolldown/plugin-babel

In v6, Babel transforms require @rolldown/plugin-babel (an optional peer dep). It is not installed — it's absent from the resolved lock file entry at pnpm-lock.yaml:13898-13904.

The codebase conditionally passes a babel config to viteReact() when React Compiler is enabled (getViteConfig.ts:147-156):

viteReact(
  reactCompiler
    ? {
        babel: {
          generatorOpts: {compact: true},
          plugins: [['babel-plugin-react-compiler', reactCompiler]],
        },
      }
    : {},
),

If v6 silently drops the babel option when @rolldown/plugin-babel is absent, the React Compiler integration would break without any error. Needs verification that v6's babel option still works for babel-plugin-react-compiler without that peer dep (since babel-plugin-react-compiler is listed as optional deps in the resolved entry, it may still work via a different code path).

---

ℹ️ Node.js Engine Requirement Tightened

v6 requires node: ^20.19.0 || >=22.12.0 — this specifically excludes Node 20.0.0–20.18.x. Confirm CI and deployment environments meet this requirement.

---

✅ No Issues

• Import/usage: The import (import viteReact from '@vitejs/plugin-react') and the call signature viteReact({...}) are unchanged and compatible with v6's API.
• Test mock at getViteConfig.test.ts:22-24 mocks the module entirely, so no test changes needed.
• Only one consumer: packages/@sanity/cli/src/actions/build/getViteConfig.ts — scope is contained.

---

Recommendation: Block this PR until vite is upgraded to ^8.0.0 in the catalog and the babel option behavior with @rolldown/plugin-babel absent is validated.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​vitejs/​plugin-react@​6.0.1

View full report

[binoy14]

Needs manual upgrade

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 6.x releases. But if you manually upgrade to 6.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.