chore(deps)(deps-dev): bump vite from 5.4.21 to 8.0.11#86
chore(deps)(deps-dev): bump vite from 5.4.21 to 8.0.11#86dependabot[bot] wants to merge 1 commit into
Conversation
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
Warning
|
| Layer / File(s) | Summary |
|---|---|
DevDependency Pin package.json |
Bumped devDependencies.vite from ^5.4.19 to ^8.0.10. |
Wiring / Scripts package.json |
Existing npm scripts (e.g., dev, build, preview, build:dev) remain unchanged in this diff but will execute using Vite v8 when run. |
Tests / CI (implicit) .github/... (no files changed) |
No CI or test files were modified in this PR; pipeline verification against Vite v8 is not included here. |
Estimated code review effort
🎯 1 (Trivial) | ⏱️ ~2 minutes
Poem
🐰 I nudged a version, light and quick,
From five to eight with a gentle click.
Builds may dance in a brighter hue,
A tiny hop — the code says "new".
🚥 Pre-merge checks | ✅ 4 | ❌ 1
❌ Failed checks (1 warning)
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Description check | A descrição do PR não segue o template obrigatório do repositório. Está em inglês, falta a seção de descrição em português, tipo de mudança, issue relacionada, checklist de validação e informações sobre como testar. | Reformule a descrição seguindo o template português obrigatório: adicione 📝 Descrição, 🎯 Tipo de mudança (marque ⚡ Performance ou 💥 Breaking change), 🔗 Issue relacionada, ✅ Checklist completo, 🧪 Como testar e |
✅ Passed checks (4 passed)
| Check name | Status | Explanation |
|---|---|---|
| Docstring Coverage | ✅ Passed | No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. |
| Linked Issues check | ✅ Passed | Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | ✅ Passed | Check skipped because no linked issues were found for this pull request. |
| Title check | ✅ Passed | O título descreve claramente a mudança principal: atualização da dependência Vite de versão 5.4.21 para 8.0.11. |
✏️ Tip: You can configure your own custom pre-merge checks in the settings.
✨ Finishing Touches
📝 Generate docstrings
- Create stacked PR
- Commit on current branch
Comment @coderabbitai help to get the list of available commands and usage tips.
![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
🤖 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 179: The package.json upgrade to "vite": "^8.0.10" requires bumping the
companion dependencies that currently reject Vite 8: update
"@vitejs/plugin-react-swc" (the package name in package.json) to a version that
lists Vite ^8 support (e.g., ^3.11.x → ^3.11.0+ or latest that includes ^8
peerDep) and update "vitest" to a version that supports Vite 8 (e.g., bump
"vitest" to ^3.2.4→ a 3.x release compatible with Vite 8 or the latest 3.x that
declares Vite ^8), then run npm install to ensure no peer dependency conflicts;
also add an "engines": { "node": ">=16" } (or your required minimum) field to
package.json to guard CI/local Node versions.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 634406a6-5bfb-4f2f-8a94-3a3a12b9b53e
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
package.json
| "tailwindcss-animate": "^1.0.7", | ||
| "typescript": "^5.5.3", | ||
| "vite": "^5.4.19" | ||
| "vite": "^8.0.10" |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== Current package.json entries =="
node -e 'const p=require("./package.json"); console.log({
vite: p.devDependencies?.vite,
pluginReactSwc: p.devDependencies?.["@vitejs/plugin-react-swc"],
vitest: p.dependencies?.vitest ?? p.devDependencies?.vitest,
enginesNode: p.engines?.node ?? "<missing>"
})'
echo
echo "== Published metadata =="
npm view vite@8.0.10 engines --json
npm view `@vitejs/plugin-react-swc`@3.11.0 peerDependencies --json
npm view `@vitejs/plugin-react-swc`@latest version peerDependencies --json
npm view vitest@3.2.4 dependencies.vite peerDependencies --json
echo
echo "== Lockfile presence and resolved entries =="
fd -HI '^(package-lock\.json|pnpm-lock\.yaml|yarn\.lock)$' .
rg -n --iglob '*lock*' '"vite"|@vitejs/plugin-react-swc|vitest@|vite@' || trueRepository: adm01-debug/Promo_Gifts
Length of output: 4698
🌐 Web query:
vitest vite 8 compatibility supported versions
💡 Result:
Vitest (latest version 4.1.5 as of 2026-05-04) is fully compatible with Vite 8. It supports Vite versions ^6.0.0 || ^7.0.0 || ^8.0.0, as specified in its peerDependencies. This range includes the stable Vite 8 (released March 2026), with explicit support added via GitHub issues #9587 (support Vite 8 beta, Feb 2026) and #9862 (drop beta support after Vite 8.0.0 stable, March 2026). Vitest 4.0 requires Vite >=6.0.0 minimum (per migration guide), and Vitest 4.1 includes "full Vite 8 support" (InfoQ announcement). Vite's supported versions (8.0 regular patches, 7.3 important fixes) align within Vitest's range. Some edge cases like coverage with third-party plugins exist but do not affect core compatibility.
Citations:
- 1: feat: support vite 8 beta, fix type issues in the config with different vite versions vitest-dev/vitest#9587
- 2: fix: drop vite 8.beta support vitest-dev/vitest#9862
- 3: https://vitest.dev/guide/migration.html
- 4: https://www.infoq.com/news/2026/05/vitest-4-1-ai-agents/?topicPageSponsorship=3179dfc3-cbfb-4eea-a3f4-da27b5b729be
- 5: https://github.com/vitest-dev/vitest/releases
- 6: https://vite.dev/blog/announcing-vite8
- 7: https://www.npmjs.com/package/vitest/v/3.0.3?activeTab=dependencies
- 8: @vitest/mocker 4.1.0: vite declared as optional peer dependency but imported unconditionally in dist/node.js vitest-dev/vitest#9915
- 9: https://registry.npmjs.org/vitest
- 10: https://www.npmjs.com/package/vitest/v/4.0.0-beta.10
- 11: https://github.com/vitest-dev/vitest
Align Vite and companion dependencies for this major upgrade.
Upgrading to vite@^8.0.10 requires updating both @vitejs/plugin-react-swc@^3.11.0 (Line 173) and vitest@^3.2.4. The current versions explicitly reject Vite 8:
@vitejs/plugin-react-swc@3.11.0peer dep:vite ^4 || ^5 || ^6 || ^7(no ^8 support)vitest@3.2.4dependency:vite ^5.0.0 || ^6.0.0 || ^7.0.0(no ^8 support)
Without upgrading both, npm install will fail. Also, add engines.node to prevent unsupported Node versions in CI/local usage.
Proposed manifest adjustment
"devDependencies": {
"@vitejs/plugin-react-swc": "^4.0.1",
"vite": "^8.0.10",
- "vitest": "^3.2.4"
+ "vitest": "^4.0.0"
},
+ "engines": {
+ "node": ">=20.19.0 || >=22.12.0"
+ }
}Verify: npm install should resolve cleanly without peer dependency conflicts.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@package.json` at line 179, The package.json upgrade to "vite": "^8.0.10"
requires bumping the companion dependencies that currently reject Vite 8: update
"@vitejs/plugin-react-swc" (the package name in package.json) to a version that
lists Vite ^8 support (e.g., ^3.11.x → ^3.11.0+ or latest that includes ^8
peerDep) and update "vitest" to a version that supports Vite 8 (e.g., bump
"vitest" to ^3.2.4→ a 3.x release compatible with Vite 8 or the latest 3.x that
declares Vite ^8), then run npm install to ensure no peer dependency conflicts;
also add an "engines": { "node": ">=16" } (or your required minimum) field to
package.json to guard CI/local Node versions.
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vite-8.0.10
branch
3 times, most recently
from
0f93250 to
234c585
Compare
There was a problem hiding this comment.
♻️ Duplicate comments (1)
package.json (1)
179-179:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAlign Vite companion packages with the Vite 8 bump.
Line 179 upgrades Vite to
^8.0.10, but Lines 173/164/118 keep older@vitejs/plugin-react-swcand Vitest 3.x packages. That combination is likely to produce peer-resolution conflicts or inconsistent tooling behavior. Please bump the companion packages together (plugin + vitest + coverage) to versions that explicitly support Vite 8, and ensureengines.nodematches Vite 8 requirements.#!/bin/bash set -euo pipefail echo "== Local manifest versions ==" node -e 'const p=require("./package.json"); console.log({ vite: p.devDependencies?.vite, pluginReactSwc: p.devDependencies?.["@vitejs/plugin-react-swc"], vitest: p.dependencies?.vitest ?? p.devDependencies?.vitest, coverageV8: p.dependencies?.["@vitest/coverage-v8"] ?? p.devDependencies?.["@vitest/coverage-v8"], enginesNode: p.engines?.node ?? "<missing>" })' echo echo "== Published compatibility metadata ==" npm view 'vite@8.0.10' engines --json npm view '@vitejs/plugin-react-swc@3.11.0' peerDependencies --json npm view 'vitest@3.2.4' peerDependencies dependencies.vite --json npm view '@vitest/coverage-v8@3.2.4' peerDependencies --json🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@package.json` at line 179, Update companion devDependencies to versions that explicitly support Vite 8: bump `@vitejs/plugin-react-swc`, vitest, and `@vitest/coverage-v8` to releases that list Vite 8 in their peerDependencies (e.g., plugin-react-swc ~3.11.x and vitest/@vitest/coverage-v8 ~3.2.x), and update the package.json "engines.node" field to the Node range required by Vite 8; ensure all three dependency names (`@vitejs/plugin-react-swc`, vitest, `@vitest/coverage-v8`) and "engines.node" are changed together so peer-resolution is consistent.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Duplicate comments:
In `@package.json`:
- Line 179: Update companion devDependencies to versions that explicitly support
Vite 8: bump `@vitejs/plugin-react-swc`, vitest, and `@vitest/coverage-v8` to
releases that list Vite 8 in their peerDependencies (e.g., plugin-react-swc
~3.11.x and vitest/@vitest/coverage-v8 ~3.2.x), and update the package.json
"engines.node" field to the Node range required by Vite 8; ensure all three
dependency names (`@vitejs/plugin-react-swc`, vitest, `@vitest/coverage-v8`) and
"engines.node" are changed together so peer-resolution is consistent.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 9087a200-9961-4bab-9d38-eace1338bc8f
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
package.json
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vite-8.0.10
branch
4 times, most recently
from
d5f4b9e to
93e7625
Compare
|
@coderabbitai full review Generated by Claude Code |
|
Tip For best results, initiate chat on the files or code changes.
[full_review] |
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vite-8.0.10
branch
2 times, most recently
from
af690aa to
6067fb4
Compare
|
🔴 Parecer técnico — SEGURAR. NÃO mergear Tipo: Build tool MEGA major (5.4.19 → 8.0.10) — pula 2 majors inteiros (v6 e v7) Saltar de Vite 5 → 8 é uma das migrações de maior risco possíveis em frontend tooling. Cada major do Vite trouxe:
Plugins afetados (quase certo precisarão upgrade junto):
Para o PromoGifts especificamente:
Recomendação: fechar este PR como will not adopt now e configurar Dependabot pra ignorar majors do Vite ecosystem: # .github/dependabot.yml
ignore:
- dependency-name: vite
update-types: [version-update:semver-major]
- dependency-name: "@vitejs/*"
update-types: [version-update:semver-major]Reabrir manualmente Q3/Q4 2026, em PR único orquestrado (vite + plugins + vitest juntos). — Claude (housekeeping de PRs, 08/05/2026) |
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 5.4.21 to 8.0.11. - [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/v8.0.11/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 8.0.10 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vite-8.0.10
branch
from
6067fb4 to
4f0ca04
Compare
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Fechando — vite 5→8 é major bump grande (+5102/-3335 linhas em package-lock, 5 checks falhando) e arrisca conflitar com a faxina em curso (Fases 1-7 do plano de cleanup). Vamos retomar este bump após Fase 6 da faxina (qualidade/lint), quando o repo estiver mais estável e tivermos largura de banda pra debugar potenciais breaking changes do Vite 8 (ex: change em SSR, plugins, build config). Por enquanto vite@5.4.x continua atendendo bem o projeto. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
1 participant
Bumps vite from 5.4.21 to 8.0.11.
Release notes
Sourced from vite's releases.
... (truncated)
Changelog
Sourced from vite's changelog.
... (truncated)
Commits
66f3194release: v8.0.115c0cfcbfix(deps): update all non-major dependencies (#22382)555ff36chore(deps): update rolldown-related dependencies (#22383)b31fd35refactor: remove unnecessary async (#22296)3c8bf06refactor: devtools integration (#22312)7c2aa3bfix: make separate object instance for each environment (#22276)3f80524feat: update rolldown to 1.0.0-rc.18 (#22360)0c162e9refactor: show direct path type in bad character warning (#22339)672c962fix(deps): update all non-major dependencies (#22334)30028f9fix(glob): align hmr matcher options with glob enumeration (#22306)