build(deps-dev): bump vite from 7.3.1 to 8.0.0#1388
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Greptile SummaryThis is an automated Dependabot PR bumping Key changes pulled in by Vite 8:
Issues worth addressing before merging:
Confidence Score: 3/5
Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[packages/ui build] --> B[vite 8.0.0]
B --> C[rolldown 1.0.0-rc.9\nreplaces rollup]
B --> D[lightningcss 1.32.0\nnew CSS processor]
B --> E[oxc-project runtime 0.115.0\nnew JS toolchain]
B --> F{Node.js engine check}
F -->|"^20.19.0 or >=22.12.0"| G[Build succeeds]
F -->|"< 20.19.0 e.g. Node 18.x"| H[Build fails]
B --> I[vite-tsconfig-paths detected]
I --> J[Deprecation warning emitted\nVite 8 has built-in TS path support]
C --> K[Platform binaries installed\ndarwin, linux, win32, android...]
Last reviewed commit: "build(deps-dev): bum..." |
| "process": "^0.11.10", | ||
| "rollup": "^4.59.0", | ||
| "vite": "^7.3.1", | ||
| "vite": "^8.0.0", |
There was a problem hiding this comment.
^20.19.0 || >=22.12.0
Vite 8 (via its bundled rolldown and @oxc-project/runtime dependencies) enforces a strict engine requirement of ^20.19.0 || >=22.12.0. This is a significant step up from Vite 7, which supported older Node.js releases.
The CI workflow (.github/workflows/test.yml) currently uses node-version: [20.x], which resolves to the latest 20.x patch on the runner. As of the time of this PR that should be ≥ 20.19.0, so CI itself is likely fine — but any developer or deployment environment still on Node 18.x or Node 20.0.0–20.18.x will fail to install/run Vite 8. It would be worth documenting this new requirement in the project's contributing guide or README, and considering pinning the CI matrix to 20.19.x (or 22.x) explicitly to make the minimum version requirement clear and enforceable.
| @@ -73,7 +73,7 @@ | |||
| "postcss": "^8.5.6", | |||
| "process": "^0.11.10", | |||
| "rollup": "^4.59.0", | |||
There was a problem hiding this comment.
rollup devDependency is now redundant with Vite 8
Vite 8 replaces rollup with rolldown as its underlying bundler. The lock file confirms rollup is now marked as "peer": true (a peer dependency of the old vite 7 entry) rather than a direct runtime dependency of Vite 8. Keeping "rollup": "^4.59.0" as a devDependency in this package is likely dead weight and could cause confusion about which bundler is actually in use. Consider removing it unless another tool in the build pipeline explicitly requires it.
| "rollup": "^4.59.0", | |
| "vite": "^8.0.0", |
| "vite": "^7.3.1", | ||
| "vite": "^8.0.0", | ||
| "vite-plugin-css-injected-by-js": "^4.0.1", | ||
| "vite-tsconfig-paths": "^6.1.1" |
There was a problem hiding this comment.
vite-tsconfig-paths
The Vite 8 changelog explicitly calls out a new warning: "warn when vite-tsconfig-paths plugin is detected" (see #21781). This is because Vite 8 now natively resolves TypeScript paths from tsconfig.json, making the plugin redundant.
vite-tsconfig-paths is used in packages/ui/vite.config.mts:
import tsconfigPaths from 'vite-tsconfig-paths';
// ...
plugins: [react(), tsconfigPaths({ root: '.' }), cssInjectedByJsPlugin()],Every Vite build or dev-server start will now emit a deprecation warning. It is worth removing the vite-tsconfig-paths dependency and its usage from the vite config and relying on Vite 8's built-in path resolution instead.
538cd07 to
69dccf7
Compare
ba45732 to
8225f8b
Compare
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 7.3.1 to 8.0.0. - [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/create-vite@8.0.0/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 8.0.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
8225f8b to
5aa8fa3
Compare
|
Superseded by #1408. |
Bumps vite from 7.3.1 to 8.0.0.
Release notes
Sourced from vite's releases.
... (truncated)
Changelog
Sourced from vite's changelog.
... (truncated)
Commits
ea68a88chore(deps): update rolldown-related dependencies (#20810)693d255release: v7.1.798a3484fix(hmr): wait forimport.meta.hot.prunecallbacks to complete before runni...9f32b1dfix(hmr): trigger prune event when import is removed from non hmr module (#20...9f2247cfix(deps): update all non-major dependencies (#20811)105abe8fix(glob): handle glob imports from folders starting with dot (#20800)4c4583cfix(build): fix ssr environmentemitAssets: truewhen `sharedConfigBuild: t...9bc9d12fix(client): use CSP nonce when rendering error overlay (#20791)54377f7release: v7.1.688af2aefix(deps): update all non-major dependencies (#20773)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 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)