I recently migrated my Angular application from version 10 to version 19 following the official migration guide. The upgrade process went smoothly and my app is running without any issues. However, I’m now encountering a problem when trying to install new packages via npm.
Every time I attempt to install a new package, I get dependency resolution errors unless I use the --force flag. The error message shows conflicts between different package versions, particularly with ng-recaptcha expecting Angular 17 while my project is now on Angular 19.
The error indicates:
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! Found: @angular/[email protected]
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"^17.0.0" from [email protected]
Is this normal behavior after a major version upgrade? Should I be concerned about using --force for new installations, or does this indicate that my migration wasn’t completed correctly? Will this cause problems down the road?
This dependency conflict is expected, not a sign you messed up the migration. ng-recaptcha still targets Angular 17 while you’re on 19 - package maintainers always lag behind Angular’s release cycle. Using --force works fine here since Angular has solid backward compatibility between major versions. But I’d go with npm install --legacy-peer-deps instead - it’s less aggressive and tracks dependencies better. Also check if ng-recaptcha has any beta/RC versions for Angular 19. I’ve managed several Angular upgrades and these mismatches usually sort themselves out in 2-3 months once the ecosystem catches up.
Yeah, this is super common with Angular v19 since you’re on the bleeding edge. ng-recaptcha just hasn’t updated their peer dependencies for Angular 19 yet, but it’ll probably work fine. I’ve run tons of packages with version mismatches in production - no real problems. The --force flag skips npm’s strict dependency checks, which is totally fine here. Just test everything thoroughly in dev first. You might want to check for a newer ng-recaptcha version or switch to @angular/google-recaptcha - they usually keep up with Angular releases better. Your migration probably went fine. This is just what happens when you’re an early adopter.
totally feel you! major upgrades can be a pain with dependencies. ng-recaptcha seems slow to catch up to v19, using --force is a quick fix for now. just stay on top of updates to avoid future headaches.