Skip to content

chore(deps): update dependency vite to v7#9

Merged
SamuelIVX merged 2 commits into
mainfrom
renovate/vite-7.x
Jan 28, 2026
Merged

chore(deps): update dependency vite to v7#9
SamuelIVX merged 2 commits into
mainfrom
renovate/vite-7.x

Conversation

@SamuelIVX
Copy link
Copy Markdown
Owner

@SamuelIVX SamuelIVX commented Jan 28, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

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

Release Notes

vitejs/vite (vite)

v7.3.1

Compare Source

Please refer to CHANGELOG.md for details.

v7.3.0

Compare Source

Please refer to CHANGELOG.md for details.

v7.2.7

Compare Source

Please refer to CHANGELOG.md for details.

v7.2.6

Compare Source

7.2.6 (2025-12-01)

v7.2.4

Compare Source

Bug Fixes

v7.2.3

Compare Source

Bug Fixes
Performance Improvements
Miscellaneous Chores

v7.2.2

Compare Source

Bug Fixes

v7.2.1

Compare Source

⚠ BREAKING CHANGES
Features
Rolldown-Vite changelogs

See rolldown-vite changelog

v7.2.0

Compare Source

Bug Fixes
  • css: fallback to sass when sass-embedded platform binary is missing (#​21002) (b1fd616)
  • module-runner: make getBuiltins response JSON serializable (#​21029) (ad5b3bf)
  • types: add undefined to optional properties for exactOptionalProperties type compatibility (#​21040) (2833c55)
Miscellaneous Chores

v7.1.12

Compare Source

Please refer to CHANGELOG.md for details.

v7.1.11

Compare Source

Bug Fixes
Miscellaneous Chores
Code Refactoring
Build System

v7.1.10

Compare Source

Bug Fixes
Documentation
Miscellaneous Chores

v7.1.9

Compare Source

Reverts

v7.1.8

Compare Source

Bug Fixes
Documentation
Miscellaneous Chores

v7.1.7

Compare Source

Bug Fixes
  • build: fix ssr environment emitAssets: true when sharedConfigBuild: true (#​20787) (4c4583c)
  • client: use CSP nonce when rendering error overlay (#​20791) (9bc9d12)
  • deps: update all non-major dependencies (#​20811) (9f2247c)
  • glob: handle glob imports from folders starting with dot (#​20800) (105abe8)
  • hmr: trigger prune event when import is removed from non hmr module (#​20768) (9f32b1d)
  • hmr: wait for import.meta.hot.prune callbacks to complete before running other HMRs (#​20698) (98a3484)

v7.1.6

Compare Source

Bug Fixes
  • deps: update all non-major dependencies (#​20773) (88af2ae)
  • esbuild: inject esbuild helper functions with minified $ variables correctly (#​20761) (7e8e004)
  • fallback terser to main thread when nameCache is provided (#​20750) (a679a64)
  • types: strict env typings fail when skipLibCheck is false (#​20755) (cc54e29)
Miscellaneous Chores

v7.1.5

Compare Source

Bug Fixes

v7.1.4

Compare Source

Bug Fixes
Miscellaneous Chores
Code Refactoring

v7.1.3

Compare Source

Features
Bug Fixes
Performance Improvements
Miscellaneous Chores
Code Refactoring
Tests

v7.1.2

Compare Source

Bug Fixes
Miscellaneous Chores

v7.1.1

Compare Source

Bug Fixes
Miscellaneous Chores
Code Refactoring
Build System

v7.1.0

Compare Source

Features
Bug Fixes
Performance Improvements
Miscellaneous Chores
Code Refactoring
Tests
Beta Changelogs
7.1.0-beta.1 (2025-08-05)

See 7.1.0-beta.1 changelog

7.1.0-beta.0 (2025-07-30)

See 7.1.0-beta.0 changelog

v7.0.8

Compare Source

Please refer to CHANGELOG.md for details.

v7.0.7

Compare Source

Please refer to CHANGELOG.md for details.

v7.0.6

Compare Source

Features
Bug Fixes
Performance Improvements
Miscellaneous Chores
Code Refactoring
Tests
Beta Changelogs
7.1.0-beta.1 (2025-08-05)

See 7.1.0-beta.1 changelog

7.1.0-beta.0 (2025-07-30)

See 7.1.0-beta.0 changelog

v7.0.5

Compare Source

Bug Fixes
Miscellaneous Chores
Code Refactoring

v7.0.4

Compare Source

Bug Fixes
  • allow resolving bare specifiers to relative paths for entries (#​20379) (324669c)
Build System

v7.0.3

Compare Source

Bug Fixes
Miscellaneous Chores
Code Refactoring
  • minor changes to reduce diff between normal Vite and rolldown-vite (#​20354) (2e8050e)

v7.0.2

Compare Source

Bug Fixes

v7.0.1

Compare Source

Bug Fixes
Miscellaneous Chores

v7.0.0

Compare Source

Vite 7 is out!

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


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 the build tool dependency to the latest major version, which may enhance build performance and stability.

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jan 28, 2026

📝 Walkthrough

Walkthrough

Updated the Vite build tool devDependency from version 6.0.5 to 7.0.0 in package.json. This is a major version bump for the development dependency with no other functional modifications.

Changes

Cohort / File(s) Summary
Build Tool Update
package.json
Vite devDependency version bumped from ^6.0.5 to ^7.0.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A newer Vite comes hopping in,
Version seven, let the builds begin!
From six to seven, smooth and fleet,
Our build tools dance, the upgrade's sweet! ✨

🚥 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 'chore(deps): update dependency vite to v7' accurately and clearly summarizes the main change: upgrading the Vite dependency from version 6 to version 7 in package.json.
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.


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

🤖 Fix all issues with AI agents
In `@package.json`:
- Line 45: Add a top-level "engines" field to package.json to enforce the Node
version required by Vite 7 and `@vitejs/plugin-react`@5.0.0; specifically add an
"engines" object with the node range ">=20.19.0 || >=22.12.0". Ensure the new
"engines" key is valid JSON at the root of package.json and that existing fields
like "devDependencies" and the "vite" entry remain unchanged.
📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0d717e0 and 9811ec7.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • package.json

✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.

Comment thread package.json
"postcss": "^8.5.1",
"tailwindcss": "^4.0.0",
"vite": "^6.0.5"
"vite": "^7.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 | 🟠 Major

🧩 Analysis chain

🌐 Web query:

Vite 7 migration guide breaking changes Node.js minimum version requirement

💡 Result:

Vite 7’s migration guide lists this breaking change for runtime support:

  • Minimum Node.js version: Node 20.19+ or Node 22.12+ (Node 18 is no longer supported). [1]
  • Why: Vite 7 is shipped ESM-only, and these Node versions are required so Node supports require(esm) without a flag (so the Vite JS API can still be required from CJS). [2]

If you’re on Node 18, you must upgrade Node or stay on Vite 6. [1]
Note: there’s a reported issue where Node 22.12.0 failed for some users and 22.13.0+ fixed it (but the official requirement remains 22.12+). [3]

Sources: [1] Vite “Migration from v6” guide, [2] Vite 7 announcement blog, [3] vitejs/vite GitHub issue #20297.


🏁 Script executed:

# Check package.json for Node version constraint and `@vitejs/plugin-react`
cat package.json | head -50

Repository: SamuelIVX/SamuelIVX.github.io

Length of output: 1342


🏁 Script executed:

# Check for lockfile and its Vite entry
ls -la | grep -E "package-lock|yarn.lock|pnpm-lock"

Repository: SamuelIVX/SamuelIVX.github.io

Length of output: 141


🏁 Script executed:

# Check full package.json to see engines field and full devDependencies
cat package.json

Repository: SamuelIVX/SamuelIVX.github.io

Length of output: 1342


🌐 Web query:

@vitejs/plugin-react 5.0.0 Vite 7 compatibility support

💡 Result:

@vitejs/plugin-react@5.0.0 explicitly supports Vite 7: its peerDependencies.vite range is ^4.2.0 || ^5.0.0 || ^6.0.0 || ^7.0.0. It also bumps the required Node version to ^20.19.0 || >=22.12.0. [1]

Vite 7’s docs also call out that @vitejs/plugin-react v5.0.0+ uses Oxc’s React refresh transform, as part of the Vite 7 / Rolldown-compatibility work. [2]

What to use with Vite 7: install/upgrade to vite@^7 + @vitejs/plugin-react@^5. [1][2]

Sources

  1. @vitejs/plugin-react@5.0.0 package.json (peerDependencies/engines) [1]
  2. Vite 7 docs (Rolldown integration note about @vitejs/plugin-react v5.0.0+) [2]

Add Node version constraint to engines field.

Vite 7 requires Node 20.19+ or Node 22.12+ (Node 18 is no longer supported). The @vitejs/plugin-react@5.0.0 version already in devDependencies is compatible with Vite 7 and also requires the same Node version range. Add an engines field to package.json to enforce this requirement:

"engines": {
  "node": ">=20.19.0 || >=22.12.0"
}
🤖 Prompt for AI Agents
In `@package.json` at line 45, Add a top-level "engines" field to package.json to
enforce the Node version required by Vite 7 and `@vitejs/plugin-react`@5.0.0;
specifically add an "engines" object with the node range ">=20.19.0 ||
>=22.12.0". Ensure the new "engines" key is valid JSON at the root of
package.json and that existing fields like "devDependencies" and the "vite"
entry remain unchanged.

@SamuelIVX SamuelIVX merged commit 659491b into main Jan 28, 2026
6 checks passed
@SamuelIVX SamuelIVX deleted the renovate/vite-7.x branch January 28, 2026 15:06
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