Angular Migrations

About 1 min reading time

In my current Angular projects, I strive to keep our growing application up-to-date with the latest stable features that Angular offers. The official migrations have been instrumental in achieving this. While some manual adjustments were necessary post-migration, the majority of my code transitioned smoothly.

Some migrations I highly recommend include:

  • inject() Functions: Migrates your application to use inject() for dependency injection.

  • Signal Inputs Migration: Converts existing @Input fields to the new signal-based input() API.

  • Signal Outputs Migration: Converts existing @Output fields to the new signal-based output() API.

  • Lazy-loaded Routes Migration: Converts eagerly loaded component routes to lazy-loaded ones.

I believe that offering migrations like these is incredibly helpful. Slowly but surely, Angular and I are becoming friends after all.


This post is based on my opinion and experience. It is based on what worked for me in my context. I recognize, that your context is different.
The "Just Sharing" Principle