chore(deps-dev): bump vite from 6.3.5 to 7.2.2 #265
Conversation
dependabot
bot
added
dependencies
dependabot
bot
added
dependencies
|
Note
|
| Cohort / File(s) | Summary |
|---|---|
Dev dependency update package.json |
Bumped devDependency vite from ^6.3.5 to ^7.2.2 |
Estimated code review effort
🎯 2 (Simple) | ⏱️ ~10 minutes
- Check build and dev scripts in
package.jsonstill run with Vite v7. - Run local dev server and production build to confirm no runtime or config errors.
Pre-merge checks and finishing touches
✅ 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 accurately describes the main change: a dev dependency update of vite from version 6.3.5 to 7.2.2, which matches the package.json modification. |
| Docstring Coverage | ✅ Passed | No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. |
✨ Finishing touches
🧪 Generate unit tests (beta)
- Create PR with unit tests
- Post copyable unit tests in a comment
- Commit unit tests in branch
dependabot/npm_and_yarn/vite-7.2.2
Comment @coderabbitai help to get the list of available commands and usage tips.
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 6.3.5 to 7.2.2. - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v7.2.2/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 7.2.2 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/vite-7.2.2
branch
from
4817989 to
9f53b09
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: Repository: lokalise/coderabbit/.coderabbit.yaml
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Jira integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
package.json(1 hunks)
| "semantic-release": "^25.0.2", | ||
| "typescript": "^5.9.3", | ||
| "vite": "^6.3.5", | ||
| "vite": "^7.2.2", |
There was a problem hiding this comment.
🧩 Analysis chain
Verify Vite 7 compatibility before merging.
This is a major version bump (6.x → 7.x). While the Dependabot PR is helpful, ensure that:
- CI/CD pipeline passes: Confirm that the build (
vite build), linting, and tests (vitest run) all pass with vite 7.2.2. - Custom vite config compatibility: The project uses
@lokalise/package-vite-config@^4.0.0. Verify this package is compatible with vite 7.x, especially given vite's significant changes (e.g., import.meta.resolve for ESM config, HTTP2 support). - Breaking changes: Vite 7 may have breaking changes. Review the Vite 7 migration guide or release notes to identify any required config updates.
To help identify potential breaking changes, please search for the official Vite 7 migration guide:
Alternatively, run the verification script below to check if the build completes successfully:
🏁 Script executed:
#!/bin/bash
# Description: Verify that the project builds and tests pass with vite 7.2.2
# Install dependencies (if needed)
npm install
# Run lint check
echo "Running lint..."
npm run lint
# Run build
echo "Running build..."
npm run build
# Run tests
echo "Running tests..."
npm run test
echo "All checks completed. If any step failed, review the error messages above."Length of output: 4296
🌐 Web query:
Vite 7 major version breaking changes migration guide
💡 Result:
Here’s a concise migration checklist for upgrading projects from Vite 6 → Vite 7, with the main breaking changes and actionable steps.
Quick actions
- Upgrade Node: require Node.js 20.19+ or 22.12+. Test CI/images accordingly. [1][2]
- Bump Vite in package.json and reinstall. Test dev and build. [1]
Major breaking changes to address
- Node/CJS → ESM distribution: Vite is ESM-distributed and no longer ships a CJS build; require Node ≥20.19/22.12. Ensure any tooling or scripts that import Vite as CJS are updated to ESM or use dynamic import wrappers. [1][2]
- build.target default changed: default target moved from "modules" → "baseline-widely-available" (higher browser minimums: Chrome 107, Edge 107, Firefox 104, Safari 16). If you relied on older browser support, explicitly set build.target to the previous value or choose a custom target. Run compatibility tests. [1]
- Sass compiler API only: legacy Sass (old API) support removed — Vite now always uses the modern Sass compiler API. If you used the legacy Sass API or relied on deprecated behavior, update your Sass usage/plugins accordingly. [5]
- Removed splitVendorChunkPlugin: if you used splitVendorChunkPlugin, remove it or replace with a custom chunking strategy. [5]
- Removed deprecated HotBroadcaster and related types/hooks: update any custom HMR internals or plugins that referenced these. [5]
- Removed some deprecated hook-level options (enforce/transform on transformIndexHtml) and other no-op deprecated properties — review custom plugins for deprecated hook signatures and types. [5]
- SSR/transform changes: avoid relying on transformed code accessing the global Object in SSR; review SSR plugin transforms and disabled experimental options like experimental.skipSsrTransform which was removed. Test SSR bundle and server rendering paths. [5]
- Environment API additions: Vite 7 adds buildApp hook and evolves Environment API — if you build frameworks/plugins against the Environment API, read the new docs and update to the buildApp/ModuleRunner patterns where applicable. [1][4]
Testing & verification
- Run full test suite (unit, integration, E2E) and CI under Node 20.19+/22.12+.
- Test dev server HMR flows, build output, SSR (if used), and library outputs.
- Audit third‑party plugins: update plugins to Vite 7–compatible versions (some plugin authors released updates at/after Vite 7). If a plugin is unmaintained, consider replacing or patching. [1][5]
Resources (read these before upgrading)
- Vite 7 announcement and migration notes. [1]
- Vite “Breaking Changes” / changes page for the full list. [2]
- Vite 7 changelog / PR summary showing removed options and exact breaking PRs. [5]
- Environment API / ModuleRunner docs if you use framework/plugin internals. [4]
References
[1] Vite — “Vite 7.0 is out!” (release announcement & migration notes).
[2] Vite — “Breaking Changes” (changes page).
[3] Vite migration/guide pages (background on Environment API & ModuleRunner).
[4] Vite — Environment API / ModuleRunner documentation.
[5] Vite changelog / PR summary for v7 (breakage list).
If you want, I can: (a) scan your package.json and plugin list for likely incompatibilities, or (b) produce a one-file migration checklist that patches common configs (node engines, build.target, remove splitVendorChunkPlugin). Which would you prefer?
---
🏁 Script executed:
```shell
#!/bin/bash
# Check npm registry for @lokalise/package-vite-config versions and vite peer dependencies
npm view @lokalise/package-vite-config versions --json | tail -20
echo "---"
npm view @lokalise/package-vite-config@latest peerDependencies --json
Length of output: 181
Revert vite upgrade to 6.x or update/replace the custom config package.
The vite 7.2.2 upgrade is incompatible with @lokalise/[email protected], which requires vite@^6.2.0. The npm install fails immediately with a peer dependency conflict:
Could not resolve dependency:
peer vite@"^6.2.0" from @lokalise/[email protected]
No vite-7-compatible version of @lokalise/package-vite-config exists in the npm registry (latest is 4.0.0, locked to vite 6.2.0).
Required action: Either revert vite to 6.x, or coordinate with the @lokalise/package-vite-config maintainer to release a vite-7-compatible version before merging this change. This PR will fail CI/CD as-is.
🤖 Prompt for AI Agents
In package.json around line 37, the upgrade to "vite": "^7.2.2" conflicts with
@lokalise/[email protected] which requires vite@^6.2.0; to fix, either
revert the vite entry to a 6.x range (e.g. ^6.2.0) and run npm install to
restore peer-compatibility, or replace/upgrade @lokalise/package-vite-config to
a vite-7-compatible alternative (or remove the custom config and inline a vite 7
config) and verify npm install and CI pass before merging.
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Bumps vite from 6.3.5 to 7.2.2.
Release notes
Sourced from vite's releases.
... (truncated)
Changelog
Sourced from vite's changelog.
... (truncated)
Commits
572aacarelease: v7.2.2728c8eefix: revert "refactor: use fs.cpSync (#21019)" (#21081)a532e68release: v7.2.182d2d6cfix(worker): some worker asset was missing (#21074)f83264frefactor(build): renameindexOfMatchInSlicetofindPreloadMarker(#21054)8293de0release: v7.2.02833c55fix(types): add undefined to optional properties for exactOptionalProperties ...e3a6a83chore(deps): update rolldown-related dependencies (#21047)b1fd616fix(css): fallback to sass when sass-embedded platform binary is missing (#21...ad5b3bffix(module-runner): makegetBuiltinsresponse JSON serializable (#21029)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for vite since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Summary by CodeRabbit