chore(deps-dev): bump vite from 6.4.2 to 8.0.10#23
chore(deps-dev): bump vite from 6.4.2 to 8.0.10#23dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
dependabot
Bot
added
dependencies
Greptile SummaryThis PR upgrades Confidence Score: 5/5Safe to merge — purely a dev dependency bump with no runtime impact and a simple config that is compatible with Vite 8. Vite is a devDependency only; the project's vite.config.ts uses no advanced Rollup/esbuild-specific options that would be affected by the Rolldown switch. The vitest peer is correctly re-resolved in the lock file. No P0 or P1 findings. No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[pnpm install] --> B[vite 8.0.10]
B --> C{Build mode?}
C -->|dev| D[Vite Dev Server 127.0.0.1:5173]
C -->|build| E[Rolldown bundler - Replaces Rollup]
D --> F[HMR + Proxy /api to port 4000]
D --> G[arkorStudioToken plugin transformIndexHtml]
E --> H[dist/ output with sourcemaps]
B --> I[vitest 4.1.5 test runner]
Reviews (1): Last reviewed commit: "chore(deps-dev): bump vite from 6.4.2 to..." | Re-trigger Greptile |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0e616cf801
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "@vitejs/plugin-react": "^4.3.0", | ||
| "typescript": "^5", | ||
| "vite": "^6.0.0", | ||
| "vite": "^8.0.10", |
There was a problem hiding this comment.
This commit upgrades vite to ^8.0.10 but leaves @vitejs/plugin-react on the 4.x line, and the lockfile still declares that plugin’s peer range as vite: ^4.2.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 (pnpm-lock.yaml), so the dependency set is now out of peer contract. In repos or CI that enforce peer correctness (strict-peer-dependencies=true) installs will fail, and even when installs proceed this combination is explicitly unsupported and can break React transform/HMR behavior; @vitejs/plugin-react should be upgraded to a major that supports Vite 8.
Useful? React with 👍 / 👎.
|
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting |
7 similar comments
|
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting |
|
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting |
|
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting |
|
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting |
|
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting |
|
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting |
|
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting |
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vite-8.0.10
branch
2 times, most recently
from
68c7729 to
5f6e6f1
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 6.4.2 to 8.0.10. - [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.10/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
force-pushed
the
dependabot/npm_and_yarn/vite-8.0.10
branch
from
5f6e6f1 to
f415486
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f4154861cd
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "@vitest/coverage-v8": "^4.1.5", | ||
| "tailwindcss": "^4.0.0", | ||
| "typescript": "^5", | ||
| "vite": "^6.0.0", | ||
| "vite": "^8.0.10", |
There was a problem hiding this comment.
This change bumps vite to ^8.0.10 but keeps @vitejs/plugin-react on the 4.x line, which is outside that plugin’s declared peer range for Vite 8 (the lockfile entry for @vitejs/plugin-react@4.7.0 still declares vite: ^4.2.0 || ^5.0.0 || ^6.0.0 || ^7.0.0). In environments that enforce peer correctness (for example strict-peer-dependencies=true), installs will fail; in non-strict installs this remains an unsupported pairing that can break React transform/HMR behavior.
Useful? React with 👍 / 👎.
Bumps vite from 6.4.2 to 8.0.10.
Release notes
Sourced from vite's releases.
... (truncated)
Changelog
Sourced from vite's changelog.
... (truncated)
Commits
32c2978release: v8.0.10a4d06d9feat: update rolldown to 1.0.0-rc.17 (#22299)a4d828ffix:hmrClient.logger.debugandhmrClient.logger.errorlooked different f...83f0a78fix(css): show filename in CSS minification warnings for.css?inline(#22292)b8a21ccfix: remove format sniffing module resolution from JS resolver (#22297)40a0847refactor: typecheck client directory (#22284)5c7cec6fix(optimizer): allow user transform.target to override default in optimizeDe...9437518refactor: enable some typecheck rules (#22278)ce729f5release: v8.0.9605bb97docs: update build CLI defaults (#22261)