-1

I'm trying to update my project from Angular 11.2 to 12, but it sends me the following error that I don't know how to solve to continue with the process. Has anyone had this problem and knows how to update it?

Installing a temporary Angular CLI versioned 12.2.18 to perform the update.
✔ Package successfully installed.
Using package manager: 'npm'
Collecting installed dependencies...
Found 91 dependencies.
Fetching dependency metadata from registry...
    Updating package.json with dependency @angular-devkit/architect @ "0.1202.18" (was "0.1100.7")...
    Updating package.json with dependency @angular-devkit/build-angular @ "12.2.18" (was "0.1100.7")...
    Updating package.json with dependency @angular-devkit/core @ "12.2.18" (was "11.2.14")...
    Updating package.json with dependency @angular-devkit/schematics @ "12.2.18" (was "11.2.14")...
    Updating package.json with dependency @angular/cli @ "12.2.18" (was "11.2.14")...
    Updating package.json with dependency @angular/compiler @ "12.2.17" (was "11.2.14")...
    Updating package.json with dependency @angular/compiler-cli @ "12.2.17" (was "11.2.14")...
    Updating package.json with dependency @angular/language-service @ "12.2.17" (was "11.2.14")...
    Updating package.json with dependency karma @ "6.4.2" (was "5.1.1")...
    Updating package.json with dependency typescript @ "4.3.5" (was "4.0.5")...
    Updating package.json with dependency @angular/animations @ "12.2.17" (was "11.2.14")...
    Updating package.json with dependency @angular/common @ "12.2.17" (was "11.2.14")...
    Updating package.json with dependency @angular/core @ "12.2.17" (was "11.2.14")...
    Updating package.json with dependency @angular/forms @ "12.2.17" (was "11.2.14")...
    Updating package.json with dependency @angular/platform-browser @ "12.2.17" (was "11.2.14")...
    Updating package.json with dependency @angular/platform-browser-dynamic @ "12.2.17" (was "11.2.14")...
    Updating package.json with dependency @angular/router @ "12.2.17" (was "11.2.14")...
    Updating package.json with dependency zone.js @ "0.11.8" (was "0.10.3")...
  UPDATE package.json (4632 bytes)
(node:22126) [DEP0147] DeprecationWarning: In future versions of Node.js, fs.rmdir(path, { recursive: true }) will be removed. Use fs.rm(path, { recursive: true }) instead
(Use `node --trace-deprecation ...` to show where the warning was created)
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: datasld@4.2.1
npm ERR! Found: @angular-devkit/build-angular@0.1100.7
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR!   dev @angular-devkit/build-angular@"^12.2.18" from the root project
npm ERR!   peer @angular-devkit/build-angular@">=0.800.0" from @ionic/angular-toolkit@2.3.3
npm ERR!   node_modules/@ionic/angular-toolkit
npm ERR!     dev @ionic/angular-toolkit@"^2.3.3" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! dev @angular-devkit/build-angular@"^12.2.18" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @angular/compiler-cli@12.2.17
npm ERR! node_modules/@angular/compiler-cli
npm ERR!   peer @angular/compiler-cli@"^12.0.0" from @angular-devkit/build-angular@12.2.18
npm ERR!   node_modules/@angular-devkit/build-angular
npm ERR!     dev @angular-devkit/build-angular@"^12.2.18" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /Users/usuyuy/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:

update to angular 12

Heretic Monkey
  • 11,687
  • 7
  • 53
  • 122
BrainLabs
  • 1
  • 1
  • So, when you searched for the error before asking here, what did you find? – Heretic Monkey Aug 16 '23 at 21:59
  • 1
    Does this answer your question? [Fix the upstream dependency conflict installing NPM packages](https://stackoverflow.com/questions/64936044/fix-the-upstream-dependency-conflict-installing-npm-packages) – Heretic Monkey Aug 16 '23 at 21:59

0 Answers0