10 released 24 June 2020, latest 10.2.5.
Angular 10 reached end of life on 24 December 2021.
What changed
Angular 10 updated the framework and CLI around newer TypeScript tooling, introduced a more configurable default browser target, and added build-time warnings when CommonJS or AMD dependencies may prevent build optimizations. The compiler and language-service tooling received improvements, and Angular Material added date-range selection support. This was also a transition-era release: some older APIs and configuration patterns were deprecated in preparation for later removals. 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 10 has reached end of life, so it no longer receives vendor security fixes, bug fixes, or compatibility work. Remaining on it increases the chance that browser changes, Node.js upgrades, TypeScript upgrades, and third-party package updates will expose unsupported combinations. The longer a codebase remains on this line, the more likely its dependencies, build configuration, tests, and custom schematics will diverge from the assumptions made by current Angular tooling. Teams also miss subsequent framework improvements and may face a larger, riskier multi-version upgrade later.
What to do
Plan an upgrade from Angular 10 through the supported Angular migration path rather than attempting to jump versions without running the intervening migrations. Start with a clean build and passing test suite, inventory Angular packages, Angular Material, RxJS, TypeScript, Node.js, browser targets, and custom builders or schematics. Use the Angular Update Guide for the target version and run the corresponding Angular CLI migrations in a branch or staging environment. Resolve deprecated APIs, CommonJS dependency warnings, strict template or compiler errors, and browser-target changes as they appear. Validate production builds, server-side rendering if used, Material components, and end-to-end tests at each upgrade step, then deploy after confirming the target runtime and CI environment are supported.
We can tell you what moving off Angular 10 involves.
What it takes to move off Angular 10 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