Migrating from AngularJS to Angular proposal. Is this a valid path forward?

I am contracting with a company that has an AngularJS application that they "eventually" want migrated to Angular, but the project I am on will have a lot of brand new development (pages and components) that they want in Angular. They do not have the setup finished to the hybrid app set up.

I had a thought to get up and running and got it going with a PoC to build an Angular 17 library. Any new components and pages could be built here then pretty easily included in the current project with downgradeComponent (got this working). Existing components can be slowly pulled out into the library as time allows. Then I am imagining that when they are ready to fully go to Angular, they can replace the current AngularJS project and if they don't want the library, it should be pretty easy to just move Angular code over to the Angular project. But they could keep the library for any reusable components as well. This also lets us get going quickly as we don't have to mess around with their current build process for building the AngularJS app.

A big push for me to think about doing this is the current folder structure is a bit messy with using AngularJS and Razor... So this would give us the opportunity of getting a much more standard and clean project structure that is pulled out of the existing messy repo.

But I am not the most expert Angular developer and this is my first time working in it professionally and wanted to get some advice on more seasoned Angular devs if the library approach for migrating is valid, or if it will potentially have more problems later and should be avoided.

Continue reading...