npm unable to resolve dependency tree for @4.0.0 (angular-devkit/architect)

[squio]

This issue looks exactly like #437 again; adding --force does work

This is caused by the mismatch of angular-devkit/architect versions @^0.1200.0 vs @^0.1202.2
The newest patch release appears to work just fine.

At the same time it is rather scary to run any npm update with the force flag everytime.

I understand there is little the ionic team can do here, still reporting so others are aware of the issue.

Found: @angular-devkit/architect@0.1202.0
npm ERR! node_modules/@angular-devkit/architect
npm ERR!   @angular-devkit/architect@"^0.1202.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular-devkit/architect@"^0.1200.0" from @ionic/angular-toolkit@4.0.0
npm ERR! node_modules/@ionic/angular-toolkit
npm ERR!   dev @ionic/angular-toolkit@"^4.0.0" from the root project

[Sampath-Lokuge]

This works for me: npm i --save-dev "@angular-devkit/architect@0.1200.5

[distante]

Hi @mhartington is this dependency fixed to ^0.1200.0 for some reason or a PR changing this would be welcomed?

[bchehraz]

I too am having a similar issue going from angular 11 to 12 on Ionic 6 rc.0. I also feel using the force flag is risky...

[Julien-Marcou]

I have the same issue.

@ionic/angular-toolkit v4.0.0 has a peer dependency to @angular-devkit/architect ^0.1200.0 which means it's only able to fetch @angular-devkit/architect v0.1200.5 at the moment (instead of v0.1202.10), so if you try to upgrade to Angular v12.1.X or v12.2.X you'll get this error.

[RowTracker]

Please will you issue an update to support @angular 12.2.x. By not doing so and using --force to install @ionic/angular-toolkit, it results in npm reporting critical compatibility errors, for example npm audit fix won't work, adding cordova plugins etc all keep reporting @ionic/architect-toolkit as breaking compatibility.

To avoid this, I tried downgrading @Angular-devkit/architect to 0.1200.10. The problem with this is that this version fails if NPM is above 7.5.6 or Node above 14.0.0. However if you read the Ionic documentation regarding installing/upgrading Ionic, the first thing it says to do is make sure you have installed the latest version of Node and NPM.

I appreciate that this problem is caused by the non-standard semver numbering of @angular-toolkit/architect but that does not help developers like me.

I know I'm repeating myself but please issue an update to fix this issue.

[Ionitron]

🎉 This issue has been resolved in version 5.0.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[HenleyCoder]

wow! that was a really speedy response, thanks.