Strategies for keeping Ionic (5+) Angular and all it's dependencies up-to-date?

Hello, I’m wondering if there are docs or resources on how to incrementally keep Ionic and Angular up to date? Seems like all the docs are going from major version to major version, but I’m wondering how to just incrementally keep up to date, especially with Angular. Should I just check in on the changelog and follow that? Is there another way?

I get nervous just running npm i @ionic/angular@x.xx.xx --save every so often…idk if I should be updating Angular incrementally? Same with NGRX, etc.

It feels like I’m missing something, so just wanted to ask.


And of course test the update before you commit/change it tonmaster branch

And still u will be banging your head checking the various dependencies as not all continue to work when updating angular. Including ngrx

I am not really following the release schedule and update every 6 months. Mostly because the dependencies have not updated yet or even the updates are buggy

Thanks. Yea, I think Ionic should just explicitly point to in the docs just so people know for sure. Especially, b/c I think there used to be an upgrade utility or something.

But, fingers-crossed it gets easier and easier, Ionic Angular Overview | Angular Version Support and Tooling.

Ionic supports Angular 6.0.0 and up . As part of their upgrade strategy, Angular has built-in tooling to help automate upgrades and provide feedback to developers whenever changes to an API occurred. This reduces update friction and keeps the ecosystem in a evergreen state.

Not sure if I agree - there is so much to document around frameworks = Angular, Vue, ReactJs. Can’t burden Ionic with it. But that is my opinion and also why this forum is important. Many people sometimes seem to struggle more with the framework then with UI of Ionic.

Right. I probably wasn’t clear. I was trying to say that Ionic should just explicitly point to the respective framework docs. I wasn’t trying to say they should recreate them.

Right now, since there isn’t anything saying, “if you are using Angular, reference update.angular and use their docs to keep your framework up-to-date.” It is basically expected that you will infer that you should go back to the frameworks. I did eventually come to that conclusion, but I was always wondering that maybe I’m just missing some document page, blog post, or release note that tells me otherwise.

That being said, the docs for starting projects is great, and the release notes are great.

You are fully right

A large portion of questions can be answered by going to sites like

The attractiveness of Ionic lies in its beautiful and easy UI.

Until you find yourself in the depths of everything underneath it!