fix(deps): resolve Babel peer-dependency conflict blocking npm ci#1043
Conversation
Two prior Dependabot PRs bumped @babel/plugin-transform-runtime and @babel/preset-react to 8.0.1, which require @babel/core@^8.0.0 — but @babel/core and the rest of the toolchain (@babel/preset-env, @babel/plugin-proposal-class-properties, etc.) are still on 7.x. This conflict breaks `npm ci` for every job on every branch, since the base branch itself carries the broken lockfile state. Revert both packages to 7.29.7 (their prior working version) rather than force the full stack to 8.x — that's a much larger breaking-change migration (4 open Dependabot PRs are attempting it: #1002, #1004, #1007, #1026, all either conflicting with each other or not yet merged) that deserves its own dedicated PR with full test coverage, not a same-day hotfix. npm ci, npm run lint:all, and npm run test (72 suites / 668 tests) all pass against current develop with this change. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request downgrades @babel/plugin-transform-runtime and @babel/preset-react from version 8.0.1 to 7.29.7 in package.json and updates the dependency tree in package-lock.json. There are no review comments, and I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
|
Warning Review limit reached
Next review available in: 48 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughBabel development dependencies are adjusted in ChangesBabel tooling alignment
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related issues
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
github-actions
Bot
added
status:needs-review
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
🔍 Reviewer Summary for PR #1043CI Status: ✅ Recommendations
|
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
github-actions
Bot
added
area:documentation
Resolves the merge conflict from PR #1043 (Babel peer-dependency fix) landing on develop after this branch already carried the same fix locally. package.json/package-lock.json merged cleanly (identical resulting babel versions); CHANGELOG.md had a duplicate "Babel peer-dependency conflict" entry from both sides, consolidated into one referencing the canonical fix (#1042, PR #1043).
1 participant
Linked issues
Fixes #1042
Context
npm ciondevelop, which cascades into every CI job (lint, test, validate, mermaid checks, etc.) on every branchdevelopand any branch based on itReproduction
develop2) Runnpm ciERESOLVEpeer-dependency conflict, install abortsRoot Cause
Two prior Dependabot PRs bumped
@babel/plugin-transform-runtimeand@babel/preset-reactto8.0.1, which require@babel/core@^8.0.0.@babel/coreitself (and the rest of the toolchain —@babel/preset-env,@babel/plugin-proposal-class-properties, etc.) are still on7.x, so npm's dependency resolver can't satisfy both constraints.Fix Summary
Revert
@babel/plugin-transform-runtimeand@babel/preset-reactto7.29.7(their prior working version) and regeneratepackage-lock.json. This is the minimal, safe unblock — a full migration to Babel 8 across the whole toolchain is a separate, larger effort already underway via 4 open Dependabot PRs (#1002, #1004, #1007, #1026), which conflict with each other and aren't ready to merge as a set.Verification
npm cisucceedsnpm run lint:allpassesnpm run testpasses (72 suites / 668 tests)Risk & Rollback
Changelog
Fixed
@babel/plugin-transform-runtimeand@babel/preset-reactfrom8.0.1to7.29.7, resolving anERESOLVEpeer-dependency conflict with@babel/core@7.xthat was breakingnpm cirepo-wide. (npm ci fails on develop: Babel peer-dependency conflict (@babel/core 7.x vs 8.x) #1042)Checklist (Global DoD / PR)