chore(deps-dev): bump @vitejs/plugin-react from 4.7.0 to 6.1.0 in /frontend - #5257
Conversation
Bumps [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react) from 4.7.0 to 6.1.0. - [Release notes](https://github.com/vitejs/vite-plugin-react/releases) - [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite-plugin-react/commits/plugin-react@6.1.0/packages/plugin-react) --- updated-dependencies: - dependency-name: "@vitejs/plugin-react" dependency-version: 6.1.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
|
blocked on author decision -- skipping (auto-mergeability sweep) This PR is BLOCKED. Root cause: the Generated by Claude Code |
|
✨ auto-fixed: merged latest main into branch (was BEHIND), CI re-running Generated by Claude Code |
|
✨ auto-fixed: merged latest main into branch to bring it up to date Generated by Claude Code |
|
✨ auto-fixed: merged latest main into branch (branch was BEHIND) Generated by Claude Code |
|
·@·d·ependabot r·ebase Generated by Claude Code |
2 similar comments
|
·@·d·ependabot r·ebase Generated by Claude Code |
|
·@·d·ependabot r·ebase Generated by Claude Code |
|
·@·d·ependabot r·ebase The npm lock file has a conflict with current main that can't be resolved without running Generated by Claude Code |
|
·@·d·ependabot r·ebase Generated by Claude Code |
6 similar comments
|
·@·d·ependabot r·ebase Generated by Claude Code |
|
·@·d·ependabot r·ebase Generated by Claude Code |
|
·@·d·ependabot r·ebase Generated by Claude Code |
|
·@·d·ependabot r·ebase Generated by Claude Code |
|
·@·d·ependabot r·ebase Generated by Claude Code |
|
·@·d·ependabot r·ebase Generated by Claude Code |
|
·@·d·ependabot r·ebase Generated by Claude Code |
vivekchand
left a comment
There was a problem hiding this comment.
Test plan & review notes
Repo: vivekchand/clawmetry
What changed
@vitejs/plugin-reactbumped 4.7.0 → 6.1.0 in/frontend— two major versions; this plugin drives JSX transform and React Fast Refresh in the Vite pipeline
Smoke commands
cd frontend
npm ci
npm run build # catches plugin API breakage immediately
# If a dev server script exists:
npm run dev & # confirm HMR / Fast Refresh banner in browser consoleWhat to look at visually (replay locally)
- Open
http://localhost:8900, edit any frontend component → confirm hot reload fires without a full page refresh - Check browser console for React Fast Refresh errors or deprecation warnings
Likely failure modes from the diff
- Plugin v5/v6 dropped legacy JSX transform options (
fastRefresh,babelshim paths changed) — ifvite.config.*passes custom@vitejs/plugin-reactoptions, they may need updating include/excludeRegExp changed in v6; components outsidesrc/that opt into JSX may silently stop being transformed- This is a more significant bump than the visx or zustand ones — worth doing a quick
npm run buildbefore merging
Staleness check — the frontend still uses this plugin; the bump is valid. Blocked purely by drift-bot, not by code rot.
Current blocker
drift-bot required check failing — needs factory.8090.ai blueprint update. Recommend clearing that gate for the whole dependabot queue at once rather than PR-by-PR.
Generated by Claude Code
|
✨ auto-fixed: merged latest main into branch (was BEHIND; no conflicts) Generated by Claude Code |
No release can publish. `release-on-merge.yml` runs `npm ci` in frontend/ and it has been failing ERESOLVE, so the [RELEASE] merge for #5055 produced no PyPI upload at all -- and neither will any other, until this lands. npm error While resolving: @vitejs/plugin-react@4.7.0 npm error Found: vite@8.2.2 npm error dev vite@"^8.2.2" from the root project npm error peer vite@"^4.2.0 || ^5.0.0 || ^6.0.0 || ^7.0.0" from @vitejs/plugin-react@4.7.0 Cause: #5376 (dependabot, "bump esbuild and vite") took vite to ^8.2.2 and left @vitejs/plugin-react at ^4.7.0, which peers only up to ^7. The two are separate dependabot PRs, so nothing checked them together, and the break is invisible on every PR -- only the release path runs this step. @vitejs/plugin-react 6.1.0 peers vite ^8.0.0 (its three other peers are marked optional), so the bump is the whole fix. Dependabot #5257 proposes that bump but touches package.json ONLY. `npm ci` requires package.json and package-lock.json to agree, so merging it alone swaps one npm ci failure for another. Both files are updated here. Verified by running the release step's own commands, not by reading: before, from origin/main: npm ci -> exit 1, ERESOLVE (reproduced locally) after: npm ci -> exit 0, 86 packages npm run build -> exit 0, bundle emitted in 509ms Deliberately minimal: package.json and package-lock.json only. The build rewrote clawmetry/static/v2/dist with fresh content hashes and that churn is reverted -- the release workflow rebuilds the bundle fresh ("Build v2 React bundle (fresh)"), so the committed dist is not what ships, and a smaller diff is worth more on a pipeline-unblocking change. No-PRD: restores a broken release pipeline; no product surface changes. Claude-Session: https://claude.ai/code/session_01Xb6A5G74JiMe3zHFs1JZEP Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
vivekchand
left a comment
There was a problem hiding this comment.
Test plan & review notes
Repo: vivekchand/clawmetry
What changed
@vitejs/plugin-reactbumped 4.7.0 → 6.1.0 in/frontend— two major versions (v5 skipped), a significant dev-dependency jump
Why this matters
v6 of @vitejs/plugin-react updated the Babel/SWC integration, dropped some legacy JSX transform options, and tightened its peer dependency on Vite itself. The build is the main gate.
Smoke commands
cd frontend
npm ci
npm run build # catch any broken Babel plugin config or JSX transform errors
npx tsc --noEmit 2>/dev/null || true # surface type issues independentlyWhat to check if the build passes
- Dev-server HMR still triggers on
.tsxfile saves (npm run dev, edit a component, check the browser refreshes without a full reload) - No
[vite] Internal server erroron the first page load afternpm run dev
Likely failure modes from the diff
- The
plugins: [react()]call invite.config.tsmay needbabeloption updates if the project was passing custom Babel options to the old API - If
@vitejs/plugin-reactis now pinned to a Vite v6+ peer dep but the project uses Vite v5, you'll see a peer-dep warning or hard error at startup
Current blocker
drift-bot (8090 Software Factory) required check is failing — needs a blueprint update at factory.8090.ai before the E2E Gate passes.
Generated by Claude Code
|
✨ auto-fixed: merged latest main into branch to bring it up to date Generated by Claude Code |
|
✨ auto-fixed: merged main into branch (was BEHIND; no conflict) Generated by Claude Code |
|
✨ auto-fixed: merged latest main into branch (BEHIND → up-to-date). Generated by Claude Code |
|
·@·d·ependabot r·ebase Generated by Claude Code |
|
·@·d·ependabot r·ebase Generated by Claude Code |
Bumps @vitejs/plugin-react from 4.7.0 to 6.1.0.
Release notes
Sourced from @vitejs/plugin-react's releases.
... (truncated)
Changelog
Sourced from @vitejs/plugin-react's changelog.
... (truncated)
Commits
39b3173release: plugin-react@6.1.0 (#1428)f1340b0feat(react): add native React Compiler support (#1419)9ab698efix(deps): update all non-major dependencies (#1375)68c0cb8release: plugin-react@6.0.5 (#1362)555cdbcfix(react): make the react compiler preset filter linear (#1353)a00a9f8fix(deps): update all non-major dependencies (#1327)f4b5498release: plugin-react@6.0.47a40659fix(react):$RefreshSig$ is not definedwith NODE_ENV=production vite dev ...98b32d4fix(deps): update react 19.2.8 (#1298)8ae5449fix: babel-plugin-react-compiler cannot be imported when used in a framework ...Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for
@vitejs/plugin-reactsince 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 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)