On a fresh install of the template, running npm install results in this compile error:
Code: Select all
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @angular-devkit/build-angular@13.2.6
npm ERR! Found: karma@5.1.1
npm ERR! node_modules/karma
npm ERR! dev karma@"~5.1.0" from the root project
npm ERR! peer karma@"*" from karma-jasmine@4.0.1
npm ERR! node_modules/karma-jasmine
npm ERR! dev karma-jasmine@"~4.0.0" from the root project
npm ERR! peer karma-jasmine@">=1.1" from karma-jasmine-html-reporter@1.7.0
npm ERR! node_modules/karma-jasmine-html-reporter
npm ERR! dev karma-jasmine-html-reporter@"^1.5.0" from the root project
npm ERR! 1 more (karma-jasmine-html-reporter)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional karma@"^6.3.0" from @angular-devkit/build-angular@13.2.6
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR! dev @angular-devkit/build-angular@"~13.2.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: karma@6.4.0
npm ERR! node_modules/karma
npm ERR! peerOptional karma@"^6.3.0" from @angular-devkit/build-angular@13.2.6
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR! dev @angular-devkit/build-angular@"~13.2.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.
Is there a cleaner solution to this?