Error when I create a new Angular project

Hello everyone,

why when i run “ionic start photo-gallery tabs --type = angular --capacitor” I can’t create a new project?

I get these errors:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: ionic-app-base@0.0.0
npm ERR! Found: @ angular / compiler @ 12.1.5
npm ERR! node_modules / @ angular / compiler
npm ERR! @ angular / compiler @ “~ 12.1.1” from the root project
npm ERR! peer @ angular / compiler @ “12.1.5” from @ angular / compiler-cli @ 12.1.5
npm ERR! node_modules / @ angular / compiler-cli
npm ERR! dev @ angular / compiler-cli @ “~ 12.1.1” from the root project
npm ERR! peer @ angular / compiler-cli @ “^ 12.0.0 || ^ 12.1.0-next” from @ angular-devkit / build-angular @ 12.1.4
npm ERR! node_modules / @ angular-devkit / build-angular
npm ERR! dev @ angular-devkit / build-angular @ “~ 12.1.1” from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @ angular / compiler @ “12.2.2” from @ angular / localize @ 12.2.2
npm ERR! node_modules / @ angular / localize
npm ERR! peerOptional @ angular / localize @ “^ 12.0.0 || ^ 12.1.0-next” from @ angular-devkit / build-angular @ 12.1.4
npm ERR! node_modules / @ angular-devkit / build-angular
npm ERR! dev @ angular-devkit / build-angular @ “~ 12.1.1” 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/luca/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/luca/.npm/_logs/2021-08-20T11_01_53_118Z-debug.log
[ERROR] An error occurred while running subprocess npm.

    npm i --save -E @ capacitor / core @ latest exited with exit code 1.
    
    Re-running this command with the --verbose flag may provide more
    information.

Installing dependencies may take several minutes.

────────────────────────────────────────────────────────────────────── ────────────

    Ionic Appflow, the mobile DevOps solution by Ionic

       Continuously build, deploy, and ship apps 🚀
    Focus on building apps while we automate the rest 🎁

             👉 https://ion.link/appflow 👈

────────────────────────────────────────────────────────────────────── ────────────

npm i
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: photo-gallery@0.0.1
npm ERR! Found: @ angular / compiler @ 12.1.5
npm ERR! node_modules / @ angular / compiler
npm ERR! @ angular / compiler @ “~ 12.1.1” from the root project
npm ERR! peer @ angular / compiler @ “12.1.5” from @ angular / compiler-cli @ 12.1.5
npm ERR! node_modules / @ angular / compiler-cli
npm ERR! dev @ angular / compiler-cli @ “~ 12.1.1” from the root project
npm ERR! peer @ angular / compiler-cli @ “^ 12.0.0 || ^ 12.1.0-next” from @ angular-devkit / build-angular @ 12.1.4
npm ERR! node_modules / @ angular-devkit / build-angular
npm ERR! dev @ angular-devkit / build-angular @ “~ 12.1.1” from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @ angular / compiler @ “12.2.2” from @ angular / localize @ 12.2.2
npm ERR! node_modules / @ angular / localize
npm ERR! peerOptional @ angular / localize @ “^ 12.0.0 || ^ 12.1.0-next” from @ angular-devkit / build-angular @ 12.1.4
npm ERR! node_modules / @ angular-devkit / build-angular
npm ERR! dev @ angular-devkit / build-angular @ “~ 12.1.1” 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/luca/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/luca/.npm/_logs/2021-08-20T11_01_56_167Z-debug.log
[ERROR] An error occurred while running subprocess npm.

    npm i exited with exit code 1.
    
    Re-running this command with the --verbose flag may provide more
    information.