chore(deps): align workspace on vite 8#3859
Merged
Merged
Conversation
With vitest 2->4 (facebook#3850) and the single-vite-7 catalog (facebook#3847) landed, the remaining vite 8 step is a version alignment: - catalog: vite ^7.3.6 -> ^8.1.3 (8.1.4 is still inside the 7-day minimumReleaseAge window) - root @vitejs/plugin-react ^4.3.0 -> ^5.2.0: 4.x peers stop at vite 7, 5.2.0 supports vite ^4-^8. plugin-react 6 is vite-8-only and adds a react-compiler peer, so it is left for a follow-up. - the standalone example apps and the vibe-tests preview app pin vite ^8.1.3 + plugin-react ^5.2.0 by hand — they live outside the workspace, so the catalog bump does not reach them - packages/build keeps "vite": "catalog:" as its peer (storybook and sandbox still depend on it in-workspace; a floating peer range is how the two-vite split of 2e64c59 happened), which narrows its published peer to ^8.1.3 on the next release Verified: exactly one vite (8.1.3) in the lockfile; storybook tsc and a full storybook build on rolldown; root (6247 tests) and docsite (217) suites green; packages/build builds. vibe-tests preview:build fails identically on main with vite 7 (missing tailwind.css import and a directory alias) — pre-existing, not a vite 8 regression.
meta-cla
Bot
added
the
CLA Signed
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
community
Contributor
PR Analysis ReportNo new or modified components detected. Bundle Size Summary
Accessibility AuditStatus: No accessibility violations detected. Generated by PR Enrichment workflow | View full report |
cixzhang
approved these changes
Jul 12, 2026
github-actions
Bot
removed
the
needs:code-review
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Final step of the incremental vite migration: with vitest 2→4 (#3850) and the single-vite-7 catalog (#3847) landed, align the whole workspace on vite 8.
vite: ^7.3.6→^8.1.3— 8.1.4 is still inside the 7-dayminimumReleaseAgewindow, so ^8.1.3 is the newest installable pin. The workspace consumers (root test config,packages/build's peer) move together.@vitejs/plugin-react^4.3.0 → ^5.2.0 — 4.x peers stop at vite 7; 5.2.0 supports vite ^4–^8 with an unchanged default API. plugin-react 6 is vite-8-only and adds a react-compiler peer, so it's left as a follow-up.apps/example-vite,apps/example-vite-tailwind(workspace-excluded templates since fix(deps): align workspace on single vite 7, drop vite override #3847) andinternal/vibe-tests/appnow pinvite ^8.1.3+plugin-react ^5.2.0, a peer-coherent pair for standalone installs. The catalog bump can't reach them.packages/buildkeeps"vite": "catalog:"as its peer — storybook and sandbox still depend on it in-workspace, and a floating peer range is how the two-vite split fixed in fix(deps): align workspace on single vite 7, drop vite override #3847 originally happened. Note this narrows the published peer to ^8.1.3 on the next release; widening it back (e.g.^7 || ^8anchored by a catalog devDependency) is a separate decision if vite 7 consumers need support.Verification
@vitejs/plugin-react@5.2.0resolved against it.pnpm peers checkshows only the two pre-existing issues (mcp-handler, unplugin 3), unchanged from before.apps/storybooktsc --noEmitpasses — the surface that broke during the original vite 6/8 split (Plugin/HotUpdate type mismatch).packages/buildbuilds.vibe-tests preview:buildfails, but identically on main with vite 7 (unresolvable../tailwind.cssimport and an alias pointing at thepackages/themes/neutral/srcdirectory) — verified against a clean main worktree; pre-existing, not a vite 8 regression.