Vovy reads your npm error, finds the package version clash behind it, and fixes it properly instead of blindly using --force.
npm install fails with ERESOLVE unable to resolve dependency tree, fix it
How it works
- Capture the full error: Vovy runs npm install and reads the whole log, not just the red line, to find which two packages disagree.
- Explain the clash: A card shows the conflict, like a library that wants React 18 while you have React 19. These are called peer dependencies: packages that must match each other.
- Check Node and lockfiles: Vovy confirms your Node version matches the project and checks for mixed lockfiles, like package-lock.json next to bun.lockb.
- Apply the smallest fix: Vovy upgrades the outdated package if a compatible version exists, or uses --legacy-peer-deps only when that is the safe choice.
- Prove it builds: Vovy reinstalls cleanly, runs npm run build, and shows a diff of what changed in package.json.
What you provide
- The project that will not install
- The error output
What you get
- npm install working
- The conflict explained in plain English
- A build that passes
- A small, reviewable package.json diff
FAQ
Can't I just run npm install --force?
It often gets you past the error, but it can install versions that break at runtime. It is a last resort, not a fix.
Is deleting node_modules safe?
Yes. It is just downloaded packages and npm recreates it. Deleting package-lock.json is riskier because it can upgrade things.
Why does it work on Lovable but not on my Mac?
Your Node or npm version is probably different. Vovy matches your local version to what the project expects.
Related tasks
All tasks