Skip to main content

How would you migrate a legacy AngularJS app to Angular (2+)?

Migrating a legacy AngularJS app to Angular (2+) is a multi-step process that involves strategic planning, gradual refactoring, and leveraging Angular’s Upgrade Module (@angular/upgrade). The goal is to run both frameworks side by side temporarily and progressively move toward a full Angular architecture.

How would you migrate a legacy AngularJS app to Angular (2+)?

🔁 Migration Strategy Overview (Step-by-Step)

✅ 1. Assess and Audit the AngularJS App

  • Inventory of all components, services, directives, filters

  • Identify areas of complexity (e.g., custom directives, stateful services)

  • Map routing and state management approaches (e.g., $stateProvider, $scope, $rootScope)

✅ 2. Prepare the AngularJS App

  • Upgrade to AngularJS 1.7.x (last LTS version)

  • Use component-based architecture (.component() instead of .controller() and .directive())

  • Ensure strict DI annotations for compatibility with AOT

✅ 3. Set Up the Hybrid App (Angular + AngularJS)

Use Angular’s @angular/upgrade module:

npm install @angular/upgrade

Create a hybrid bootstrap using UpgradeModule:

import { platformBrowserDynamic } from '@angular/platform-browser-dynamic';
import { UpgradeModule } from '@angular/upgrade/static';
import { AppModule } from './app/app.module';
import { angularjsApp } from './legacy-app';

platformBrowserDynamic().bootstrapModule(AppModule).then(platformRef => {
  const upgrade = platformRef.injector.get(UpgradeModule);
  upgrade.bootstrap(document.body, [angularjsApp.name], { strictDi: true });
});

✅ 4. Migrate Services and Components Gradually

🡒 Downgrade Angular services/components for use in AngularJS:

import { downgradeInjectable } from '@angular/upgrade/static';
angular.module('app').factory('newService', downgradeInjectable(NewService));

🡒 Upgrade AngularJS services/components for use in Angular:

import { upgradeComponent } from '@angular/upgrade/static';

@Component({
  selector: 'legacy-widget',
  template: '<div>{{ data }}</div>',
})
class LegacyWrapperComponent {}

@NgModule({
  declarations: [LegacyWrapperComponent],
  entryComponents: [LegacyWrapperComponent],
})
class AppModule {
  constructor(upgrade: UpgradeModule) {
    upgrade.upgradeNg1Component('legacyWidget');
  }
}

✅ 5. Route Partitioning

  • Use AngularJS routing for legacy views, Angular Router for new views

  • Optionally use ui-router hybrid to manage routing across both

✅ 6. Move Feature-by-Feature

  • Start with isolated features (e.g., a form or dashboard widget)

  • Build new features in Angular only

  • Gradually replace AngularJS views, services, directives with Angular equivalents

✅ 7. Remove AngularJS

  • Once all features are migrated, remove UpgradeModule

  • Clean up legacy code and dependencies

🧠 Best Practices

  • Keep Angular and AngularJS code in separate folders (/legacy, /app)

  • Use shared services for data access (migrated early)

  • Avoid deep coupling between AngularJS and Angular parts

  • Automate tests to ensure functional parity

🧪 Tools That Help

Popular posts from this blog

Explain the Angular compilation process: View Engine vs. Ivy.

 The Angular compilation process transforms your Angular templates and components into efficient JavaScript code that the browser can execute. Over time, Angular has evolved from the View Engine compiler to a newer, more efficient system called Ivy . Here's a breakdown of the differences between View Engine and Ivy , and how each affects the compilation process: 🔧 1. What Is Angular Compilation? Angular templates ( HTML inside components) are not regular HTML—they include Angular-specific syntax like *ngIf , {{ }} interpolation, and custom directives. The compiler translates these templates into JavaScript instructions that render and update the DOM. Angular uses Ahead-of-Time (AOT) or Just-in-Time (JIT) compilation modes: JIT : Compiles in the browser at runtime (used in development). AOT : Compiles at build time into efficient JS (used in production). 🧱 2. View Engine (Legacy Compiler) ➤ Used in Angular versions < 9 🔍 How It Works: Compiles templat...
Read more

What are the different types of directives in Angular? Give real-world examples.

In Angular, directives are classes that allow you to manipulate the DOM or component behavior . There are three main types of directives: 🧱 1. Component Directives Technically, components are directives with a template. They control a section of the screen (UI) and encapsulate logi c. ✅ Example: @Component ({ selector : 'app-user-card' , template : `<h2>{{ name }}</h2>` }) export class UserCardComponent { name = 'Alice' ; } 📌 Real-World Use: A ProductCardComponent showing product details on an e-commerce site. A ChatMessageComponent displaying individual messages in a chat app. ⚙️ 2. Structural Directives These change the DOM layout by adding or removing elements. ✅ Built-in Examples: *ngIf : Conditionally includes a template. *ngFor : Iterates over a list and renders template for each item. *ngSwitch : Switches views based on a condition. 📌 Real-World Use: < div * ngIf = "user.isLoggedIn...
Read more

Explain the concept of ControlValueAccessor in custom form components.

 In Angular, the ControlValueAccessor interface is what allows custom form components to work seamlessly with Angular forms (both reactive and template-driven). 🧠 What is ControlValueAccessor ? It’s an Angular bridge between your custom component and the Angular Forms API . When you use a custom form component (like a date picker, dropdown, slider, etc.), Angular doesn't automatically know how to read or write its value. That’s where ControlValueAccessor comes in. It tells Angular: How to write a value to the component How to notify Angular when the component’s value changes How to handle disabled state 📦 Common Built-in Examples: <input> and <select> already implement ControlValueAccessor You implement it when creating custom form controls 🔧 Key Methods in the Interface Method Purpose writeValue(obj: any) Called by Angular to set the value in the component registerOnChange(fn: any) Passes a function to call when the component value ch...
Read more