Apps
Upgrade Ionic 4 to Ionic 5 (Angular)
07 Jun 2024 · Grant Brits
Notes from moving an Angular Ionic 4 app onto Ionic 5: dependency bumps, breaking UI changes, and the Capacitor path that keeps iOS and Android shipping.
We still get asked about Ionic 4 → 5 upgrades on Angular codebases. The short version: treat it as a controlled migration, not a weekend bump.
What usually bites
- Angular and Ionic peer dependencies need to move together. Half-upgrading leaves you in a broken peer graph.
- Ionic 5 brings CSS variable and component API changes. Custom themes and shadow-DOM styling need a pass.
- Navigation and lifecycle hooks differ enough that you should re-test every critical flow on device, not just in the browser.
- Capacitor (or Cordova plugins) need their own compatibility check before you call the upgrade done.
How we run it
- Inventory plugins, native bridges, and custom components.
- Upgrade on a branch with a checklist of screens and API calls.
- Fix styling and breaking component changes in passes, not one giant diff.
- Ship TestFlight / Play internal builds before production.
If your product is still on Ionic 4 and the store or security requirements are pushing you forward, we have done this path before, including the Laravel API behind it.