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 - 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 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 was generated by Mend Renovate. View the repository job log.

---

Note

Low Risk
Low risk dependency-only change affecting only the examples/component-tests tooling; main risk is build/test behavior changes from the new plugin major version.

Overview
Updates the examples/component-tests dev dependency @vitejs/plugin-react from ^5.2.0 to ^6.0.1 to align the example’s Vite React plugin with the latest major release.

^{Written by Cursor Bugbot for commit 95db071. This will update automatically on new commits. Configure here.}

[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: examples/component-tests/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 unable to resolve dependency tree
npm error
npm error While resolving: example-component-tests@2.1.0
npm error Found: vite@7.3.1
npm error node_modules/vite
npm error   dev vite@"^7.3.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vite@"^8.0.0" from @vitejs/plugin-react@6.0.1
npm error node_modules/@vitejs/plugin-react
npm error   dev @vitejs/plugin-react@"^6.0.1" 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-20T09_03_51_248Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-20T09_03_51_248Z-debug-0.log

[cypress-app-bot]

See the guidelines for reviewing dependency updates for info on how to review dependency update PRs.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

Plugin v6 requires Vite 8 but project uses Vite 7

High Severity

@vitejs/plugin-react v6 dropped support for Vite 7 and now requires Vite 8+. The project still declares "vite": "^7.3.1" as a dependency, making the two packages incompatible. This will likely cause a peer dependency conflict during install or a runtime failure.

Additional Locations (1)

• examples/component-tests/package.json#L20-L21

 

[MikeMcC399]

Reject this PR, since it requires Vite 8.

Defer updating to Vite 8 until feature request cypress-io/cypress#33078 is resolved, keeping both E2E and component testing in this repo on Vite 7 in the interim.

[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.