13 released 3 November 2021, latest 13.4.0.
Angular 13 reached end of life on 4 May 2023.
What changed
Angular 13 made Ivy the only rendering and compilation engine by removing View Engine support, so applications and libraries needed to be Ivy-compatible. It also removed Internet Explorer 11 support, moved the Angular Package Format toward modern ES module output and package exports, and improved build performance with persistent build caching. The cycle updated supported tooling baselines, including newer TypeScript, Node.js, and RxJS ranges, and introduced simpler APIs for dynamic component creation while deprecating older ComponentFactory-based patterns. Angular is not AngularJS: AngularJS is a separate, earlier framework with its own versions and its own end of life. Teams running AngularJS should use /technology/angularjs instead.
What staying costs
Angular 13 has reached end of life, so defects and security issues in the framework and its official tooling no longer receive fixes for this line. Its older dependency constraints can also make it harder to adopt current Node.js environments, TypeScript tooling, browser policies, and maintained third-party Angular libraries. Because Angular 13 is Ivy-only, teams that still depend on View Engine-era libraries or custom build assumptions may already have compatibility work to resolve; delaying further can increase the number of Angular major-version changes that must be handled in one migration.
What to do
Inventory the application, Angular libraries, Node.js version, TypeScript configuration, RxJS usage, browser-support requirements, and custom builders before upgrading. Remove or replace any remaining View Engine-dependent packages, update code using deprecated dynamic-component APIs where practical, and confirm that the application does not require Internet Explorer 11. Use Angular’s update guidance to move through supported major versions in controlled steps, running unit, integration, build, and browser tests at each step. Upgrade the CI and developer toolchain alongside Angular, then validate production builds, server-side rendering if used, and all internally published libraries before deployment.
We can tell you what moving off Angular 13 involves.
What it takes to move off Angular 13 depends on what you built on it — the version you are on, how much depends on it, and how much of the work is mechanical. Leave your email with this version and we can tell you what that looks like for you.
Not sure yet? Get my plan