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

[SamuelIVX]

This PR contains the following updates:

Package	Change	Age	Confidence
@vitejs/plugin-react (source)	^5.0.0 → ^6.0.0

---

Release Notes

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

v6.0.0

Compare Source

v5.2.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - "every weekday" in timezone America/New_York, 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 has been generated by Renovate Bot.

Summary by CodeRabbit

• Chores
  • Updated development dependencies to latest versions

[SamuelIVX]

⚠️ 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: 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: personal_website@0.0.0
npm error Found: vite@7.3.1
npm error node_modules/vite
npm error   dev vite@"^7.0.0" 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.0
npm error node_modules/@vitejs/plugin-react
npm error   dev @vitejs/plugin-react@"^6.0.0" 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 /tmp/renovate/cache/others/npm/_logs/2026-03-13T09_10_35_901Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-03-13T09_10_35_901Z-debug-0.log

[coderabbitai]

📝 Walkthrough

Walkthrough

A single devDependency version is bumped from version 5 to 6 in package.json. The @vitejs/plugin-react package is updated from ^5.0.0 to ^6.0.0, allowing compatibility with the latest major release of the Vite React plugin.

Changes

Cohort / File(s)	Summary
Dependency Update package.json	Bump @vitejs/plugin-react devDependency from ^5.0.0 to ^6.0.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• chore(deps): update dependency @vitejs/plugin-react to v5 #5: Also modifies the @vitejs/plugin-react devDependency version in package.json (bumped to v5), making it a related dependency update across different versions.

Poem

🐰 Vite's React plugin hops to six,
From five it makes its nimble mix,
Dependencies dance with playful cheer,
Hopping forward, full of gear! 🚀✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and accurately summarizes the main change: updating @vitejs/plugin-react dependency to version 6.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch renovate/vitejs-plugin-react-6.x

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@package.json`:
- Line 35: The `@vitejs/plugin-react` entry in package.json is bumped to ^6.0.0
but that requires vite@^8.0.0; either revert the plugin to a v5-compatible range
or upgrade vite together with lockfile. Fix by updating package.json: change
"@vitejs/plugin-react" back to "^5.0.0" if you want to defer the vite upgrade,
or update "vite" to "^8.0.0" and keep "@vitejs/plugin-react":"^6.0.0" if you
intend to upgrade both; after changing package.json run the package manager to
regenerate the lockfile (npm/yarn/pnpm install) and commit the updated lockfile
and package.json. Ensure tests/build succeed before pushing.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: d238c61e-cb3b-4b80-8a3b-8bd1b4a939ee

📥 Commits

Reviewing files that changed from the base of the PR and between f7307e0 and 74635a3.

📒 Files selected for processing (1)

• package.json

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check the peer dependency requirements for `@vitejs/plugin-react` v6
npm view `@vitejs/plugin-react`@6.0.0 peerDependencies --json

Repository: SamuelIVX/SamuelIVX.github.io

Length of output: 176

---

🏁 Script executed:

cat package.json | grep -A 1 -B 1 '"vite"'

Repository: SamuelIVX/SamuelIVX.github.io

Length of output: 190

---

Peer dependency conflict: @vitejs/plugin-react@6.0.0 requires vite@^8.0.0.

This PR cannot be merged as-is. The update to @vitejs/plugin-react@6.0.0 requires peer dependency vite@^8.0.0, but the project currently uses vite@^7.0.0. This mismatch will cause npm to fail with an ERESOLVE error during dependency resolution.

To resolve this:

1. Option A: Wait for a compatible vite v8 upgrade and bundle both updates together.
2. Option B: Keep @vitejs/plugin-react at ^5.0.0 until the project is ready to upgrade vite.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` at line 35, The `@vitejs/plugin-react` entry in package.json is
bumped to ^6.0.0 but that requires vite@^8.0.0; either revert the plugin to a
v5-compatible range or upgrade vite together with lockfile. Fix by updating
package.json: change "@vitejs/plugin-react" back to "^5.0.0" if you want to
defer the vite upgrade, or update "vite" to "^8.0.0" and keep
"@vitejs/plugin-react":"^6.0.0" if you intend to upgrade both; after changing
package.json run the package manager to regenerate the lockfile (npm/yarn/pnpm
install) and commit the updated lockfile and package.json. Ensure tests/build
succeed before pushing.

[SamuelIVX]

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.