Angular Version History AngularJS to Angular 22 — 2026 Guide

Angular ships a new major version every six months. Miss two release cycles and you’re already running something Google no longer patches. This guide tracks every Angular version — from the original AngularJS in 2010 to Angular 22 — with release dates, key features, and how long each version stays supported.

What Is Angular?

Angular is a TypeScript-based, open-source web application framework built by Google. It uses a component-based architecture, and it’s one of the three frameworks (alongside React and Vue) that most enterprise teams choose for large, long-lived web applications. If you’re evaluating whether it’s the right fit for a new build, our guide to the benefits and advantages of Angular breaks down when it makes sense.

What Is the Current Version of Angular?

Angular 22 is the current Angular version, released on June 3, 2026. It stabilizes Signal Forms and ships stable accessible components through Angular ARIA — both of which spent the previous release cycle in developer preview. If your project is still on Angular 20 or earlier, you’re at least one full support cycle behind.

Angular Version Support: Active, LTS, and EOL

This is the part most Angular version history pages skip, and it’s the part that actually matters if you’re running Angular in production.

Every major Angular release goes through three phases:

• Active support (6 months): New features, bug fixes, and security patches.
• Long-Term Support / LTS (12 months): Security and critical bug fixes only. No new features.
• End of Life (EOL): No patches of any kind, including security fixes.

That’s an 18-month lifespan per major version. With a new major every six months, there are usually two or three supported versions at any point—and a growing pile of unsupported ones still running in production somewhere.

Figure 1: Angular version support status, active through end-of-life.

A handful of CVEs were disclosed against Angular’s SSR pipeline and template compiler in late 2025—patched in Angular 19.2+, 20.3+, and 21.0.2+. If you’re on Angular 18 or older, those patches were never backported to your version. That’s the practical cost of running an EOL framework: it’s not that the code stops working, it’s that nobody is checking whether it’s still safe.

If patching your way through a sequential upgrade isn’t realistic right now, our maintenance and support services cover exactly this gap.

Complete Angular Version History (Angular 2 to Angular 22)

Angular can’t skip versions during an upgrade—you go 12 → 13 → 14, not 12 → 15. So knowing what changed at each step actually matters when you’re planning a migration, not just trivia.

Angular 2

September 2016

•       The complete TypeScript rewrite of AngularJS—new architecture, new syntax, not backward-compatible.
•       This is the release that split “AngularJS” from “Angular” as separate names.

Why was Angular 3 skipped? It wasn’t—not really. The @angular/router package had already shipped a 3.x version on its own versioning track. Rather than have the router at v3 and the framework at v2, the team aligned everything and jumped straight to Angular 4.

Angular 4

March 2017

• Backward-compatible with Angular 2. Improved router, smaller bundle sizes via AOT compilation improvements.

Angular 5

November 2017

• RxJS 5.5 support, the Angular Universal State Transfer API, and a build optimizer for production bundles.

Angular 6

May 2018

•  Angular CLI 6, Angular Material 6, RxJS 6. Introduced ng update and ng add.

Angular 7

October 2018

• Synced releases across CLI and Material. Bumped minimum dependencies to TypeScript 3.1, RxJS 6.3, Node.js 10.

Angular 8

May 2019

• Dynamic imports for lazy-loaded routes, differential loading for modern vs. legacy browsers.

Angular 9

February 2020

• Ivy became the default compiler and renderer—smaller bundles, faster tests, better debugging across the board.

Angular 10

June 24, 2020

• Raised the TypeScript floor to 3.9. Added a date range picker to Angular Material.

Angular 11

November 11, 2020

• TypeScript 4.0 support, faster package installs, better Hot Module Replacement.

Angular 12

May 12, 2021

• Tailwind CSS support, strict null checks, Webpack 5.

Angular 13

November 3, 2021

• Dropped IE 11 support entirely. RxJS 7.4 became the default. View Engine was fully retired — Ivy only from here on.

Angular 14

June 1, 2022

• Strongly-typed reactive forms and a new FormRecord type. Standalone components arrived as a developer preview.

Angular 15

November 16, 2022

• Standalone components went stable, which meant you could build an Angular app without NgModules for the first time. Directive composition API also shipped.

For a deeper look at what this release changed in practice, see our Angular 15 feature breakdown.

Angular 16

May 3, 2023

• Signal-based reactivity introduced as a developer preview. Faster hydration for server-side rendering.

Angular 17—Release Date and Features

Released November 8, 2023

• A bigger jump than the version number suggests: a new built-in control flow syntax (@if, @for, @switch) replacing *ngIf/*ngFor structural directives.
• A rebuilt rendering pipeline for faster load times.

Angular 18

May 22, 2024

• Experimental zoneless change detection and further SSR/hydration improvements.

Angular 18 strengthened its position as a top choice for enterprise full-stack development. For a practical guide on combining Angular with .NET for end-to-end solutions, read our article on Angular and .NET full-stack development.

Angular 19

November 19, 2024

• Standalone became the default for new components, directives, and pipes—NgModules are now the exception, not the rule.
• Angular 19.1.2 (January 20, 2025) followed with SSR performance fixes and bug patches.
• Angular 19 reached end of life on May 19, 2026.

Angular 20

May 28, 2025

• The Signals API—effect(), linkedSignal(), and toSignal()—moved to production-stable.
• Zoneless change detection graduated to developer preview, meaning apps can now realistically run without Zone. js.
• Incremental hydration for SSR also went stable.

Angular 21

November 19, 2025

• Signal Forms shipped as experimental, alongside experimental accessible components through Angular ARIA.
• Zoneless became the default for new apps.

Angular 22 (Latest Version)

June 3, 2026

• Signal Forms and Angular ARIA components graduated to stable.
• This is the current Angular version as of this writing.

AngularJS Version History (Angular 1.x)

AngularJS and Angular are different frameworks, not sequential versions of the same one—a distinction that trips up a lot of searches for “Angular version history.”

AngularJS 1.0 launched in 2010, created by Miško Hevery, as a JavaScript-based MVC framework for single-page applications. It introduced two-way data binding and dependency injection to a much wider audience than any framework before it. AngularJS went through its 1.x line for over a decade, with AngularJS 1.8.3 as the final release before Google ended official support on December 31, 2021.

Despite that, AngularJS hasn’t disappeared—a large number of production applications built years ago are still running on it, quietly accumulating unpatched vulnerabilities with no vendor fix coming. If that’s your situation, migrating to modern Angular is the long-term fix, but it’s rarely a quick one. Our open-source development team can help scope what that migration actually looks like for your codebase.

Angular Version Compatibility Matrix

Upgrading Angular usually means upgrading Node.js, TypeScript, and RxJS in lockstep. Here’s what pairs with what:

Figure 2: Angular / TypeScript / Node.js / RxJS compatibility by version.

Always check the exact range in the package. JSON for your target version before upgrading—minor patch releases shift these ranges more often than most teams expect.

Why Angular Version History Matters for Your Business

Three things break silently once an Angular version goes EOL: security patches stop, browser compatibility drifts as Chrome and Safari keep shipping updates, Angular was never tested against, and compliance audits (SOC 2, PCI DSS, HIPAA) flag EOL software as a finding—sometimes enough to block a deal.

None of that shows up as an error message. It shows up as risk that sits quietly until something forces the issue—a pen test, an audit, an incident. If you’re not sure which Angular version your production app is running or whether it’s still supported, that’s worth finding out before it becomes someone else’s emergency.

How to Check Your Angular Version

Run this from your project root:

ng version

Or check a specific project’s Angular core version directly:

cat package.json | grep “@angular/core”

How to Upgrade to the Latest Angular Version

npm install -g @angular/cli ng update @angular/cli @angular/core

The catch: Angular upgrades are sequential. You can’t jump from Angular 13 straight to Angular 21—you have to pass through every major version in between, and each one can carry its own breaking changes. For a handful of versions, that’s a weekend. For a team several versions behind, it’s a multi-week project with real regression-testing risk attached. That’s usually where it makes sense to bring in a team that’s done the migration before rather than debug it live—our full-stack development services cover Angular upgrades specifically, including apps built on the MEAN stack.

Frequently Asked Questions

What is the latest stable version of Angular?

Angular 22, released June 3, 2026. It’s in active support until roughly December 2026, when it moves into LTS.

What is the latest stable version of AngularJS?

AngularJS 1.8.3, released before Google ended official support on December 31, 2021. No newer AngularJS version exists or is planned.

When was Angular 17 released?

November 8, 2023. It introduced the new @if/@for control flow syntax and a faster rendering pipeline.

Why was Angular 3 never released?

It wasn’t skipped for feature reasons—the @angular/router package was already versioned at 3.x independently, so the team jumped the whole framework from 2 to 4 to keep every package’s version number aligned.

How often does Angular release a new version?

Every six months, like clockwork, since Angular 2 launched in 2016—with version 3 as the one deliberate skip.

Can I skip versions when upgrading Angular?

No. Angular requires sequential upgrades through each major version. Skipping is not supported and typically breaks the CLI’s automated migration schematics.

What is the difference between AngularJS and Angular?

AngularJS (1.x) is a JavaScript-based framework released in 2010. Angular (2+) is a complete TypeScript rewrite released in 2016. They’re separate frameworks with different architectures—not different versions of the same thing—and there’s no direct upgrade path between them.

How many major versions of Angular are there?

As of Angular 22 (June 2026), there have been 21 major releases since Angular 2—22, counting AngularJS as version 1—with version 3 skipped.

Is Angular still being actively developed?

Yes. Angular ships a new major version every six months on a predictable schedule, with Angular 22 as the latest as of this writing and future releases already signaled on Google’s public roadmap.

What Angular version should I use for a new project?

The current stable version—Angular 22 as of this writing—unless a specific library or internal dependency hasn’t caught up yet. Starting on an EOL version only means you inherit an upgrade project on day one.

Staying Current on Angular

Angular 22 is the current version as of September 2026, but that will be out of date within six months—which is exactly the problem with most “Angular version history” pages: they’re accurate the day they’re published and stale a year later.

If your team is running an older Angular version and isn’t sure whether it’s still supported or what an upgrade path actually looks like for your specific codebase, get in touch. C-Metric has worked on Angular projects ranging from single-version bumps to multi-year-behind migrations and can scope what yours would take before you commit to it.