What we do
Tools
Industries
Department
How we workLet's talk →
Home/Angular Developer for AngularJS and Old Angular
Angular Development

Angular Developer Work, From AngularJS Rebuilds to Angular 22 Upgrades

The order dashboard still loads every morning. Then someone needs one new filter on it, opens the code, and finds a version number from four or five years ago and RxJS chains nobody on staff can follow. Before you hire anyone, it helps to know which Angular you actually have, because the two answers lead to very different jobs.

AngularJS and Angular share a name, not a codebase

Open package.json. If it lists a package called angular, you're on AngularJS. If it lists @angular/core, you're on Angular, and the version number next to it tells you how far behind you are.

AngularJS (1.x)

A rebuild, done in slices

  • Templates full of ng-app, ng-controller and $scope.
  • Google's support ended at the start of 2022. No more security fixes are coming from the Angular team.
  • There's no ng update path. The screens get rebuilt in current Angular, ideally a section at a time so staff never lose the old version before the new one works.
Angular (2 and later)

An upgrade, done in steps

  • Components, TypeScript and RxJS, built with the Angular CLI.
  • Versions 2 to 19 are out of support. Angular 20's long-term support ends on 28 November 2026, Angular 21 is covered until June 2027, and Angular 22 is the active release.
  • Majors used to arrive every six months. From version 22 the plan is one a year, each supported for about two years.

An app on Angular 12 is a long upgrade. An app on AngularJS is a new front end that has to behave exactly like the old one. Quote them differently, and be wary of anyone who doesn't ask which one you have.

Five questions that show whether someone can take over your Angular app

Plenty of developers can build a new Angular screen. Fewer can open someone else's, years later, and move it forward without breaking what staff rely on.

  • "How would you get this from our version to Angular 22?"

    A good answer is one major at a time, running ng update for each and letting its migrations rewrite the code, with a build and a test run at every stop. Anyone promising one big jump hasn't done it.

  • "What do you do with a subscribe nested inside another subscribe?"

    This is the RxJS code that's hard to inherit. You want to hear about flattening operators like switchMap or concatMap, and about where each subscription gets cleaned up so screens don't leak memory or fire requests twice.

  • "Which of our libraries will block the next major?"

    Old component libraries and date pickers are usually the real blocker, not Angular itself. Libraries never rebuilt for the Ivy compiler stop working at Angular 16, when the compatibility step was removed.

  • "What happens to our Protractor tests?"

    Protractor is deprecated. If your end-to-end tests run on it, they need moving to a current tool, or the upgrade goes ahead with no safety net.

  • "Do we have to convert everything to standalone components?"

    No. Standalone has been the default since Angular 19, but NgModules still work, and Angular ships a schematic to convert gradually. A developer who wants to rewrite every module first is spending your budget on style.

Getting a stalled Angular app back onto a supported release

This is the order the work runs in when an app is several majors behind. Each step ships, so the app is never broken for weeks while the upgrade happens.

  1. 1

    Get it building exactly as it is

    Pin the Node version and every package to what the app was last built with, and get a clean build on a fresh machine. Old Angular often won't build on a current Node install, and you can't upgrade what you can't build.

  2. 2

    Put tests around the screens staff use every day

    A handful of end-to-end tests on the screens that matter, like search, edit and save, catch what the compiler won't: a form that quietly stops submitting, or a table that loads empty.

  3. 3

    Step up one major version at a time

    Each step is ng update @angular/cli@^N @angular/core@^N for the next version up, followed by a build, the tests, and a release. The CLI runs its own migrations as it goes, which is why skipping majors costs more than it saves.

    Watch for: Angular 20 is not a place to stop. Its long-term support ends on 28 November 2026, so the target is 21 at minimum, and 22 if you want the longest runway.

  4. 4

    Replace the libraries that hold it back

    When a third-party package has no version for the next major, swap it for one that does, or rebuild the component it provided. This is usually where most of the hours go.

  5. 5

    Leave the new patterns for later

    Once the app is current, standalone components, signals and the newer template syntax can come in screen by screen, as features get touched. They aren't a condition of being supported.

Let's talk

An Angular app on a supported release, with every screen still working

n-frames picks up Angular and AngularJS front ends that have fallen behind, rebuilds or upgrades them in steps that each go live, and connects them to the backend or third-party systems they need. You'll know whether it's an upgrade or a rebuild before any work is priced.

Count the steps to Angular 22 →

Questions people ask

Our Angular app is several major versions behind. How bad is that?

It depends on the gap and on what's built on top. Going from 19 to 22 is a few stops, mostly running migrations and testing. Going from 8 to 22 means working through the Ivy switch, replacing libraries that never moved, and probably retiring Protractor tests. AngularJS is a different case entirely: it's a rebuild, not an upgrade. The quote names which one you're facing, once someone has read the code.

Do you handle the backend too, or only the Angular front end?

Both. Angular front ends almost always have to talk to an API, a database or a system like an ERP or CRM, and that part often needs building or fixing too. n-frames builds the backend or the integration alongside the Angular work, so the two get tested together.

What if the Angular work is actually pretty small?

Then it's quoted as small. A new filter or one extra form on an app that's already current is a short job. If the app is several majors behind, the quote notes whether that small change can safely go in first, or whether the upgrade has to come before it.

What does the free Angular quote tell me, exactly?

Which framework you're really on, how many majors stand between you and a supported release, which libraries will block the way, and what the upgrade or rebuild costs.

Is AngularJS the same thing as Angular?

No. AngularJS is the original 1.x framework, and its support ended at the start of 2022. Angular (version 2 onward) is a rewrite in TypeScript with a different structure. Code doesn't carry across, which is why moving off AngularJS is a rebuild.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.