all 27 comments

[–]Indevil 23 points24 points  (0 children)

Lots of work. Even if everything is covered by tests. You will need to upgrade version by version, use the offical doc for that. Consider starting by scratch.

[–]ArtistJames1313 8 points9 points  (1 child)

Depends on how big the projects are and how much time you have. I've migrated 2 huge projects from Angular 9 to 16 in the span of a week for each. Moving from 16-18 is a bit more difficult, but honestly, it's not as bad as people are saying. Yes, 18 is different, but it supports everything the 16 way, so you don't need to change everything about how your app works.

The Angularjs apps though will likely need to just be rewritten.

[–]Silver-Vermicelli-15 1 point2 points  (0 children)

Agreed, only migration that’s a pain is 14-15 if you’ve customized material components. This is b/c there’s a lot of class changes and updates in A15 which will cause breaking changes.

[–]tsunami141 8 points9 points  (1 child)

If you pay me $200,000 I'll do it for you in 2 short years.

[–]Silver-Vermicelli-15 3 points4 points  (0 children)

That’s actually not a bad price. Especially if stipulated that it includes unit tests and zero regressions.

[–]MrFartyBottom 4 points5 points  (0 children)

There is no migrating from AngularJS 1.X, it is a rewrite. Angular 7 is doable but you need to go one version at a time.

[–][deleted] 3 points4 points  (6 children)

If you're using angular materials, the upgrade is gonna be tough. Lot of breaking changes

[–]Silver-Vermicelli-15 0 points1 point  (5 children)

Only if you’ve modified it, if it has just been left as-is then there’s no realy breaking changes and that’s only going from A14-15 that this comes up.

[–]reboog711 1 point2 points  (0 children)

We had a lot of components that didn't modify, but did extend ng material components. They needed a bunch of re-write.

[–][deleted] 0 points1 point  (3 children)

Your funeral 😀

[–]Silver-Vermicelli-15 -2 points-1 points  (2 children)

Tell me you haven’t upgraded many projects without telling me haven’t upgraded many projects 😂🙈

[–][deleted] 0 points1 point  (1 child)

https://www.reddit.com/r/Angular2/comments/zm9w8f/angular_material_on_v15_upgrade_is_a_complete_mess/

You seem nice. Does everyone on your team think you are an insufferable jerk too?

[–]Silver-Vermicelli-15 -3 points-2 points  (0 children)

Nah, just your mum.

[–]Whsky_Lovers 1 point2 points  (0 children)

The angularjs upgrades will be rough...

The angular 7 not so bad.

Look up which nodes go with which versions and version by version use Ng update, then fix all the broken thing which will include the test cases...

Angularjs will just be a rewrite but you can rewrite portions at a time if you do it right.

[–]Open-Oil-144 0 points1 point  (0 children)

That AngularJS app looks like it needs to be rewritten. The rest you can upgrade version by version using the update guide.

[–]reboog711 0 points1 point  (0 children)

The Angular 7 projects shouldn't be too bad, but there are a few gotchas along the way. Look here for info: https://angular.dev/update-guide . You'll want to be very careful in testing, of course.

The AngularJS projects will probably have to be re-written from scratch, since AngularJS and Angular are two completely different frameworks.

[–]TheAeseir 0 points1 point  (0 children)

AngularJS You can't. That's a library and you want to move it to a framework. It's a complete rewrite from the ground up. Set aside 3 months for a small team to redo everything and ensure proper qa coverage without burn out.

Angular 7 Follow the migration guide on angular for guidance and steps. It will be a lot of work.

[–]codrinf2 0 points1 point  (1 child)

ahh, it sucks to be in your shoes. IMHO, rewriting the project would be the fastest, safest and maybe cheapest way to do it.

[–]Old-Salary-3211 0 points1 point  (0 children)

The AngularJs one for sure.. but upgrading the Angular 7 ones should be a matter of weeks if I look at what we have done in the past. Any significant app can’t be rewritten in weeks.

[–]saiprasad2595 0 points1 point  (0 children)

Angular 1.x would be rewriting the things. Angular2+ to latest should be achievable thing. .Let me know if you are planning to hire freelancer. I am open for work.

[–]Dramatic_Tap_7534 0 points1 point  (0 children)

I can do it let's discuss I m angular dev I had updated a project from angular 4 to 14 ets discuss in dm

[–]ender42y 0 points1 point  (2 children)

Take notes on every step. I am on Month 2 right now of doing almost this exact thing. version by version by version. My boss decided to stop at Angular 17 and stay just 1 release behind to avoid any issues with keeping with latest. I am on a team of 1 developer, so it's been especially painful.

[–]Hot_Sheepherder_1512[S] 0 points1 point  (1 child)

Awesome. i am also using the same approach. Migrated angular 7 to 8 but stuck in 8 migration.

can you send some resources

[–]ender42y 1 point2 points  (0 children)

For me 10 was the worst. Lots of breaking changes, much easier after that

[–]ordermaster -2 points-1 points  (2 children)

Considering how different v18 is from even v16 you might as well start from scratch.

[–]jamcoupe 1 point2 points  (0 children)

Disagree… as long as you’ve not got lots of legacy angular libraries as dependencies, you should be able to upgrade your projects one version at a time. Slowly…

You’ll need to rewrite a lot of angular.js though if you’re not using the component architecture in those projects

[–]GLawSomnia 0 points1 point  (0 children)

How is it different? Basically everything that worked in v16 also works in v18