codelord.net

Code, Angular, iOS and more by Aviv Ben-Yosef

Modern AngularJS Migration Guide

You’ve been maintaining this AngularJS project for a while and it seems to be getting obsolete by the day

You keep hearing about components, and they sound useful, but you’re not sure how to start using them in your existing project, alongside all your controllers and directives. You worked hard to master AngularJS, yet now even in 1.x the standards are changing:
“Controllers are dead”
“Don’t use $scope”
“Avoid two-way bindings”
You see this and can’t help but wonder whether your AngularJS is still useful, or is it a dying dialect?

Keeping up with the old way of doing things is taking a daily toll on your team

It’s becoming increasingly harder to find references and people that use AngularJS like you do. You come across a bug in a library you’re using – and hey, there’s an updated version that fixes it! But that simple update becomes a nightmare when you realize it requires updating your AngularJS version, and you fear what that upgrade may break.

“What exactly is Angular 2 improving upon so much that I need to upgrade?”

What’s worse is that you keep hearing about Angular 4 (yeah, 2 is so 2016), and don’t want to be left out with a bunch of legacy code. Yet, moving to it seems crazy – it looks nothing like your code.
And Angular 4 comes with a bunch of questions:
Should you learn TypeScript?
Change all your tooling and build system?
Find alternative packages to replace those you’re currently using?

And worse of all, is Angular 4 even going to be popular, or will you spend time and effort learning it just to find yourself in the same spot a year from now? It feels like a gamble. You don’t need the “new shiny”, you need to ship features fast.

It’d be great if your app was once again something you’re proud of—a modern codebase with the latest 1.x standards where it’s easy to get stuff done… but you don’t know how to get there without a big, long rewrite.

What if you could work on a modern and clean AngularJS project?

Banging out components, reaping the benefits of better performance and standard design. You’d get work done faster and just imagine getting there while sticking to your existing deadlines, making your bosses pleased?

Yeah, upgrading your project can feel like a big unknown, with no clear steps to follow, and way too many questions, but it doesn’t have to be.

Learn how to upgrade your project to the latest AngularJS 1.6, with my no-fluff book

Get the Modern AngularJS Migration Guide and…

  • Update to the latest AngularJS and dependencies safely.
  • Understand the conceptual changes AngularJS went through.
  • Master components, their new lifecycle hooks, and how they play along with one-way data flow.
  • Follow a tried and tested path, with clear guidance.
  • Learn all about the changes along 1.0, 1.2, 1.3, 1.4 to 1.6.
  • Get the safe and small refactoring steps to get from obsolete controllers to swanky, isolated components.
  • See how components affect your unit tests and routing definitions.
  • Have a codebase that’s future-proof and compliant with a transition to Angular 4, should you ever choose to move to it later on.

Get a step by step guide for migrating to a modern codebase as you keep working

Imagine: answers on Stack Overflow actually being relevant, free performance improvements from latest updates, all feasible without risk and a big rewrite break.

To learn the quickest and safest way to work on a modern and maintainable codebase again – buy the Modern AngularJS Migration Guide. Then you’ll master the gradual approach for transitioning even the bigger projects, cool as a cucumber, and at your own pace.

Be the first to learn when it’s out (soon!)