Needs advice
Angular 2Angular 2

We are looking for a way to cope with AngularJS' LTS coming to its end. We have been working for about the last 3 years on a project, written using ASP.NET Core + AngularJS 1.5.7 + Fuse theme. Altogether we've invested about 10 development years into it. The alternatives we've looked at so far were migrating to Angular2+ or React, but we expect those alternatives to be too costly (we can't afford ourselves investing ~3 development years on such a migration project). We've also considered side-by-side development – that is leaving the current code as is, and using some more advanced technology only for new features – but we couldn't find a reasonable way to implement it, and it won't actually solve the main issue we have with the LTS ending. The main issue for us with AngularJS' LTS coming to its end is the lack of security updates that come as parts of new releases (and of course we are happy to advance to a newer technology regardless).

So which technology is the simplest to migrate to, and is there some tool or library that can help us?

5 upvotes·6.6K views
Replies (6)
Senior Software Engineer at JOOR·

Moving from AngularJS to Angular is as hard as moving to any other tool because the only thing they share is the name-ish. React is my logical decision because for me it simpler due to its use of JavaScript. You don't have magic as with Angular. You use plain JavaScript to code, and things just work. The new Angular is a copy of React (mostly). And having to work with TypeScript makes things messier. You can migrate React to TypeScript, but if you have no experience, you don't need to use it. For me React is cleaner and simpler than Angular as "the new technology to use to migrate all your codebase". You can always leave your clients with the old app, and add a button to a new and shiny app in development, and ask them to try and give feedback. Doing this, you will find what's important for them, and which parts need to be prioritized instead of migrating all from a to z. It also helps your clients to learn the application step by step instead of having a sudden change to a new app that they don't totally know. Doing this you allow them to compare the old and the new one, and find their way around easily. Hope this helps you :)

4 upvotes·2.5K views
Lead Software Engineer at Salesforce·
Angular 2

I did this migration in 2016-2017 on a pretty large app. Search "migrating from angularjs to angular" and you'll find tons of advice. And some tools. We chose to upgrade based on route, where basically more of our routes were handled by Angular over time and less by AngularJS. The whole migration took about 18 months, the app continued to work fine, and eventually, it was all migrated.

Here are some tools that can help suggest a path forward.

6 upvotes·3K views
View all (6)
Avatar of Gustavo Muñoz

Gustavo Muñoz

Senior Software Engineer at JOOR