NOOB to Angular

[Dan Arsenault]

I'm new to Angular.

I have inherited a project using AngularJS 1.4.4

It's still functional.

Any advise going forward?

- Should I learn v1.4.4, then migrate to Angular?

- Should I scrap v1.4.4, learn Angular, then migrate?

TIA

-dan

.

[Alexbyk (subscriptions)]

I guess, you should

- learn the official angularjs 1.X tutorial, this is enough for understanding angular JS (1-2 days)

- invest a time in learning angular 10, it has a steep learning curve (1-2 weeks)

- then migrate

. --
You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to angular+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/angular/3ade3f5b-0030-42ca-9867-14bbcdb54defn%40googlegroups.com.

[Richard Farkas]

Dan, how big is your application? There are different paths from AngularJS to the latest Angular. Sam Julien has an excellent resource for deciding your path and extreme detail step-by step guides at https:///www.upgradingangularjs.com if you have a small budget for that. Join Angular Nation and consider https://www.udemy.com/course/the-complete-guide-to-angular-2/

To view this discussion on the web visit https://groups.google.com/d/msgid/angular/2e2f6f3d-5b62-b764-c9f8-cbbeab59500a%40alexbyk.com.

[Aaron Frost]

My opinion is that you should take your project and turn it into an AngularJS 1.4 + Angularv11 Hybrid app. Here are some important things to look at before you do that. 

• What is your build system? Is is Gulp, Grunt, Webpack? Learning your build will help you get away from AngularJS 1.4.x faster. This is because you need to integrate your existing build with other builds. 
• Learn the Angular Hybrid model approach. You need to get your app to work along side of Angular. Look at Sam Julien's course for instructions, or read Victor Savkin's book. 
• Once you are there, you are ready to go. 

It is a long road, but you can do it. 

[phil.b...@gmail.com]

Oh lord please don't do that - it's effective only for the most simple of AngularJS applications.  When you start looking at the hoops you have to jump thru - particularly for dependency injection - you'll lose your hair.  You could probably just reimplement the functionality in Angular directly much faster....if there's a service implementation for example, that code could be copied directly with very minor modifications into an Angular service......

[d d]

Thanks for all your replies!

It's quite a large project and its build system is Maven, Gulp, Bower, etc ... (which is also new to me).

I'll start with tutorials with a pragmatic approach. I'd love to port directly to Angular, but I think it's too big and risky at this time.

[Aaron Frost]

Phil, I have using ngUpgrade on some extremely large projects and it works well. Once it is setup, it's insanely easy and beneficial. I have done it over a dozen times and it works great. 

Further, almost none of the code from an AngularJS service is Copy/Paste to an Angular service. Depending on how you wrote the service, you may be able to copy some of it. But... you wouldn't want to. Writing Promise-based services isn't anything like writing Observable-based services. 

ngUpgrade is the most supported way to go when upgrading from AngularJS to Angular. It allows you to do a slow re-write instead of a full blown re-write which comes with lots of risk.