I'm trying to upgrade from Angular 15 to Angular 16.
I had this config for version 15:
{
"name": "name",
"version": "0.0.0",
"scripts": {
"ng": "ng",
"start": "ng serve",
"build": "ng build",
"watch": "ng build --watch --configuration development",
"test": "ng test",
"lint": "ng lint"
},
"private": true,
"dependencies": {
"@angular/animations": "^15.0.4",
"@angular/common": "~15.0.4",
"@angular/compiler": "~15.0.4",
"@angular/core": "~15.0.4",
"@angular/forms": "~15.0.4",
"@angular/localize": "~15.0.4",
"@angular/platform-browser": "~15.0.4",
"@angular/platform-browser-dynamic": "~15.0.4",
"@angular/router": "~15.0.4",
"@ng-bootstrap/ng-bootstrap": "^14.0.0",
"@popperjs/core": "^2.11.6",
"bootstrap": "^5.2.0",
"ngx-spinner": "^15.0.1",
"ngx-toastr": "^15.0.0",
"rxjs": "~7.5.5",
"tslib": "^2.4.0",
"zone.js": "~0.11.5"
},
"devDependencies": {
"@angular-devkit/build-angular": "^15.0.5",
"@angular-eslint/builder": "15.1.0",
"@angular-eslint/eslint-plugin": "15.1.0",
"@angular-eslint/eslint-plugin-template": "15.1.0",
"@angular-eslint/schematics": "^15.1.0",
"@angular-eslint/template-parser": "15.1.0",
"@angular/cli": "^15.0.5",
"@angular/compiler-cli": "~15.0.4",
"@types/jasmine": "~4.0.3",
"@types/node": "^17.0.30",
"@typescript-eslint/eslint-plugin": "^5.43.0",
"@typescript-eslint/parser": "^5.43.0",
"eslint": "^8.28.0",
"eslint-plugin-jsdoc": "^39.2.9",
"jasmine-core": "~4.1.0",
"karma": "~6.3.19",
"karma-chrome-launcher": "~3.1.1",
"karma-coverage": "~2.2.0",
"karma-jasmine": "~5.0.0",
"karma-jasmine-html-reporter": "~1.7.0",
"karma-junit-reporter": "^2.0.1",
"typescript": "~4.8.4"
}
}
This is my first attempt for the new config (in order to run Angular 16):
{
"name": "name",
"version": "0.0.0",
"scripts": {
"ng": "ng",
"start": "ng serve",
"build": "ng build",
"test": "ng test",
"test-ci": "ng test --watch=false --browsers=ChromeHeadless",
"lint": "ng lint"
},
"private": true,
"dependencies": {
"@angular/animations": "^15.0.4",
"@angular/common": "16.0.0",
"@angular/compiler": "^16.0.0",
"@angular/core": "16.0.0",
"@angular/forms": "~15.0.4",
"@angular/localize": "~15.0.4",
"@angular/platform-browser": "~15.0.4",
"@angular/platform-browser-dynamic": "~15.0.4",
"@angular/router": "~15.0.4",
"@ng-bootstrap/ng-bootstrap": "^14.0.0",
"@popperjs/core": "^2.11.6",
"bootstrap": "^5.2.0",
"ngx-spinner": "^15.0.1",
"ngx-toastr": "^15.0.0",
"rxjs": "~7.5.5",
"tslib": "^2.4.0",
"zone.js": "~0.13.1"
},
"devDependencies": {
"@angular-devkit/build-angular": "16.0.0",
"@angular-eslint/builder": "16.0.0",
"@angular-eslint/eslint-plugin": "16.0.0",
"@angular-eslint/eslint-plugin-template": "16.0.0",
"@angular-eslint/schematics": "^16.0.0",
"@angular-eslint/template-parser": "16.0.0",
"@angular/cli": "16.0.0",
"@angular/compiler-cli": "16.0.0",
"@types/jasmine": "~4.0.3",
"@types/node": "^18.0.30",
"@typescript-eslint/eslint-plugin": "^5.43.0",
"@typescript-eslint/parser": "^5.43.0",
"eslint": "^8.28.0",
"eslint-plugin-jsdoc": "^39.2.9",
"jasmine-core": "~4.1.0",
"karma": "~6.3.19",
"karma-chrome-launcher": "~3.1.1",
"karma-coverage": "~2.2.0",
"karma-jasmine": "~5.0.0",
"karma-jasmine-html-reporter": "~1.7.0",
"karma-junit-reporter": "^2.0.1",
"typescript": "~4.9.4"
}
}
However, this is what I'm getting when I run "npm install":
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: name@0.0.0
npm ERR! Found: @angular-devkit/build-angular@15.0.5
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR! dev @angular-devkit/build-angular@"16.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! dev @angular-devkit/build-angular@"16.0.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: @angular/compiler-cli@16.0.0
npm ERR! node_modules/@angular/compiler-cli
npm ERR! peer @angular/compiler-cli@"^16.0.0" from @angular-devkit/build-angular@16.0.0
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR! dev @angular-devkit/build-angular@"16.0.0" 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.
Please guide me to get this to work. It could work with "--force" but I guess that's not what you want.