Before
npm install npm ERR! ERESOLVE could not resolve peer react@"^18" from package-a peer react@"^19" from package-b
Dependency repairs
Fix Node dependency conflicts without guesswork.
Peer dependency warnings become hard failures after upgrades. RinaWarp inspects package.json, lockfiles, and the errors your package manager prints.
What worked locally with `--legacy-peer-deps` breaks in CI with a clean install. The durable fix aligns versions or chooses a supported combination — not another force flag.
Dependency graphs fail in CI first
Symptoms we see often
- ERESOLVE unable to resolve dependency tree
- Duplicate copies of React or other singleton packages
- Works on one machine, fails in CI with `npm ci`
- Patch/minor bump pulled incompatible transitive deps
Common causes
- Peer dependency range too loose across project packages
- Mixing package managers or stale lockfile
- Overrides/resolutions missing for known conflicts
- Optional deps required at runtime but not installed
How RinaWarp fixes it
RinaWarp Terminal Pro follows the Observe → Plan → Approve → Execute → Proof workflow. Nothing executes without your approval.
- Read npm/pnpm error output and identify the conflicting packages
- Adjust versions, overrides, or workspace protocol as appropriate
- Reinstall with the same command CI uses
- Run build and tests to prove the graph is healthy
Before and after
Representative terminal output — your project will differ, but the verification pattern should look like this.
After verification
Aligned react peer across project packages Regenerated lockfile npm ci — success npm run build — exit 0
Related fixes
Try it on your broken project
Free tier includes daily proof workflow runs on small and medium repos. Pro ($15/mo) removes limits for serious individual use.