Skip to content

chore(deps): update dependency vite to v8#57

Closed
SamuelIVX wants to merge 1 commit into
mainfrom
renovate/vite-8.x
Closed

chore(deps): update dependency vite to v8#57
SamuelIVX wants to merge 1 commit into
mainfrom
renovate/vite-8.x

Conversation

@SamuelIVX
Copy link
Copy Markdown
Owner

@SamuelIVX SamuelIVX commented Mar 13, 2026

This PR contains the following updates:

Package Change Age Confidence
vite (source) ^7.0.0^8.0.0 age confidence

Release Notes

vitejs/vite (vite)

v8.0.0

Compare Source

Vite 8 is here!

Today, we're thrilled to announce the release of the next Vite major:

⚠ BREAKING CHANGES
  • remove import.meta.hot.accept resolution fallback (#​21382)
  • update default browser target (#​21193)
  • the epic rolldown-vite merge (#​21189)
Features
Bug Fixes
Performance Improvements
Documentation
Miscellaneous Chores
Code Refactoring
Tests
Beta Changelogs
8.0.0-beta.18 (2026-03-09)

See 8.0.0-beta.18 changelog

8.0.0-beta.17 (2026-03-09)

See 8.0.0-beta.17 changelog

8.0.0-beta.16 (2026-02-27)

See 8.0.0-beta.16 changelog

8.0.0-beta.15 (2026-02-19)

See 8.0.0-beta.15 changelog

8.0.0-beta.14 (2026-02-12)

See 8.0.0-beta.14 changelog

8.0.0-beta.13 (2026-02-05)

See 8.0.0-beta.13 changelog

8.0.0-beta.12 (2026-02-03)

See 8.0.0-beta.12 changelog

8.0.0-beta.11 (2026-01-29)

See 8.0.0-beta.11 changelog

8.0.0-beta.10 (2026-01-24)

See 8.0.0-beta.10 changelog

8.0.0-beta.9 (2026-01-22)

See 8.0.0-beta.9 changelog

8.0.0-beta.8 (2026-01-15)

See 8.0.0-beta.8 changelog

8.0.0-beta.7 (2026-01-08)

See 8.0.0-beta.7 changelog

8.0.0-beta.6 (2026-01-07)

See 8.0.0-beta.6 changelog

8.0.0-beta.5 (2025-12-25)

See 8.0.0-beta.5 changelog

8.0.0-beta.4 (2025-12-22)

See 8.0.0-beta.4 changelog

8.0.0-beta.3 (2025-12-18)

See 8.0.0-beta.3 changelog

8.0.0-beta.2 (2025-12-12)

See 8.0.0-beta.2 changelog

8.0.0-beta.1 (2025-12-08)

See 8.0.0-beta.1 changelog

8.0.0-beta.0 (2025-12-03)

See 8.0.0-beta.0 changelog

Rolldown-Vite changelogs

See rolldown-vite changelog


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
    • Upgraded build tool dependency to the latest stable release, improving development infrastructure and ensuring compatibility with recent tooling enhancements. No user-facing changes introduced.

@SamuelIVX
Copy link
Copy Markdown
Owner Author

⚠️ 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 could not resolve
npm error
npm error While resolving: @vitejs/plugin-react@5.1.4
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
npm error Could not resolve dependency:
npm error peer vite@"^4.2.0 || ^5.0.0 || ^6.0.0 || ^7.0.0" from @vitejs/plugin-react@5.1.4
npm error node_modules/@vitejs/plugin-react
npm error   dev @vitejs/plugin-react@"^5.0.0" from the root project
npm error
npm error Conflicting peer dependency: vite@7.3.1
npm error node_modules/vite
npm error   peer vite@"^4.2.0 || ^5.0.0 || ^6.0.0 || ^7.0.0" from @vitejs/plugin-react@5.1.4
npm error   node_modules/@vitejs/plugin-react
npm error     dev @vitejs/plugin-react@"^5.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_43_146Z-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_43_146Z-debug-0.log

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Mar 13, 2026

📝 Walkthrough

Walkthrough

Updated the Vite development dependency from version 7 to version 8 in package.json. This is a single-line configuration change to the project's build tooling dependency version constraint.

Changes

Cohort / File(s) Summary
Dependency Version Update
package.json
Bumped Vite devDependency from ^7.0.0 to ^8.0.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Poem

🐰 A hop, a skip, Vite takes flight,
Version eight shines bright and light,
Build tools upgrade without a fright,
Dependencies dance through the night!

🚥 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 concisely summarizes the main change: updating the vite dependency to version 8, which is the primary purpose of this changeset.
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/vite-8.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

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

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

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 45: package.json currently pins "vite": "^8.0.0" but the installed plugin
"@vitejs/plugin-react@5.1.4" is incompatible; update the dependency entry for
"@vitejs/plugin-react" to "^6.0.0" (or later) in package.json, then run npm
install to refresh dependencies and regenerate package-lock.json; ensure
package.json's vite entry remains "^8.0.0", confirm no ERESOLVE errors, and run
your build/test to verify the updated "@vitejs/plugin-react" works with the Vite
8 upgrade.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 85cf8227-5fbf-4ad7-b3ab-95f410915d4b

📥 Commits

Reviewing files that changed from the base of the PR and between f7307e0 and 940608f.

📒 Files selected for processing (1)
  • package.json
📜 Review details
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Lint Code Base

Comment thread package.json
"postcss": "^8.5.1",
"tailwindcss": "^4.0.0",
"vite": "^7.0.0"
"vite": "^8.0.0"
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

What is the first @vitejs/plugin-react release that declares peerDependencies.vite including ^8, and what is that exact peer dependency range?

💡 Result:

The first @vitejs/plugin-react release whose peerDependencies.vite range includes ^8 is 6.0.0, and the exact peer dependency range is:

  • vite: ^8.0.0 [1]

Blocker: Vite 8 upgrade currently breaks dependency resolution.

Line 45 sets vite to ^8.0.0, but the current @vitejs/plugin-react@5.1.4 only supports up to Vite 7. This causes npm ERESOLVE and prevents package-lock.json updates. Upgrade @vitejs/plugin-react to ^6.0.0 or later, which explicitly supports vite@^8.0.0.

Required update
  "devDependencies": {
-   "@vitejs/plugin-react": "^5.1.4",
+   "@vitejs/plugin-react": "^6.0.0",
    "vite": "^8.0.0"
  }
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@package.json` at line 45, package.json currently pins "vite": "^8.0.0" but
the installed plugin "@vitejs/plugin-react@5.1.4" is incompatible; update the
dependency entry for "@vitejs/plugin-react" to "^6.0.0" (or later) in
package.json, then run npm install to refresh dependencies and regenerate
package-lock.json; ensure package.json's vite entry remains "^8.0.0", confirm no
ERESOLVE errors, and run your build/test to verify the updated
"@vitejs/plugin-react" works with the Vite 8 upgrade.

@SamuelIVX SamuelIVX closed this Mar 16, 2026
@SamuelIVX
Copy link
Copy Markdown
Owner Author

Renovate Ignore Notification

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

@SamuelIVX SamuelIVX deleted the renovate/vite-8.x branch March 16, 2026 09:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants