Skip to content

Angular 20: What Actually Shipped

Angular 20 was released on 28 May 2025. This page covers what shipped, drawn from the release changelog, with the breaking changes and how to handle them.

For the release cadence, support windows and the current version, see Angular Versions and Release Cadence.

Several APIs that had been in developer preview became stable in v20:

  • linkedSignal — writable state derived from other signals. See Signals and Angular Reactivity.
  • toSignal and toObservable from @angular/core/rxjs-interop.
  • PendingTasks — the injectable that tells Angular about async work, which matters for SSR stability under zoneless.
  • afterEveryRender — renamed from afterRender and stabilised.
  • Incremental hydration — stabilised, along with withI18nSupport().

That set is the point at which the signal-based reactivity story became something you could build on without preview caveats.

provideExperimentalZonelessChangeDetection was renamed to provideZonelessChangeDetection, reflecting the move from experimental to developer preview. (Zoneless became the default later, in v21.) See Change Detection and Zoneless Angular.

Related: zone.js became an optional peer dependency.

Dynamically-created components got bindings

Section titled “Dynamically-created components got bindings”

Previously, creating a component through ViewContainerRef.createComponent meant setting inputs imperatively and wiring outputs by hand. Angular 20 added support for:

  • Input bindings on dynamically-created components
  • Two-way bindings
  • Output listeners
  • Applying directives to dynamically-created components

This closes a long-standing gap for dialog, overlay and dynamic-form libraries, which previously had to reimplement binding semantics.

Note the constraint that came with it: setInput cannot be used together with inputBinding.

ngIf, ngFor and ngSwitch are deprecated in favour of the built-in control flow blocks @if, @for and @switch.

Deprecated is not removed, and existing code keeps working — but new code should use the blocks, and there is a schematic for the conversion:

Terminal window
ng generate @angular/core:control-flow

Review the result: the schematic converts *ngFor without trackBy to track $index, which is behaviour-preserving and wrong for any list that can be reordered or have items removed from the middle. See Tracking in @for.

Angular 20 began exposing performance data to Chrome DevTools, so component rendering, change-detection cycles and lifecycle hooks appear in the browser’s own performance timeline alongside everything else. A new DI profiling event landed as part of the same work. See Angular Performance.

Three compiler changes in v20 can break existing templates, and they are the ones most likely to bite silently.

in and void are now operators. An expression like {{ void }} previously referred to a component property named void; it now refers to the operator. If you have a property with either name, write {{ this.void }}.

Parentheses are always respected. {{ (foo?.bar).baz }} now throws when foo is nullish — matching native JavaScript. Previously the safe-navigation short-circuit propagated past the parentheses.

Suspicious date patterns are detected. Using the Y formatter (week-numbering year) without also including w (week number) is flagged, because y is almost always what was intended. This one has caught real production bugs where dates around the new year rendered a year off.

  • TypeScript below 5.8 is no longer supported.
  • Node.js 18 is no longer supported, and neither are Node 22.0–22.10. The minimum was later tightened to 20.19, 22.12 or 24.0. Check before upgrading — an unsupported Node version produces confusing build failures rather than a clear message.
  • InjectFlags removed from the public API. inject, Injector.get, EnvironmentInjector.get, TestBed.get and TestBed.inject no longer accept it. Use the options object: inject(Token, { optional: true }). A migration ships with the release.
  • The any overload was removed from injector.get. It now accepts only ProviderToken<T> and (deprecated since v4) string.
  • TestBed.get removed — use TestBed.inject.
  • TestBed.flushEffects() removed — use TestBed.tick().
  • Uncaught errors in listeners are rethrown by default in tests rather than only logged. This is the change most likely to turn a previously-green suite red, and the errors it surfaces are real. Fix them, catch them where the test intentionally covers an error case, or as a last resort set rethrowApplicationErrors: false in configureTestingModule.
  • AsyncPipe reports subscription and promise errors to the ErrorHandler directly. For Zone-based applications the end result is generally the same, but the mechanism differs enough to require test updates.
  • Animations are guaranteed to be flushed when Angular runs change detection or ApplicationRef.tick. Tests asserting that DOM elements were removed may have been passing on the old, delayed behaviour.
  • ApplicationRef.tick no longer catches and reports errors to the application ErrorHandler. They are thrown out of the method so callers can decide whether to abort follow-up work or report and continue.
  • PendingTasks.run no longer returns the async function’s result. Reimplement with PendingTasks.add if you need it — and handle promise rejections, because under SSR an unhandled rejection can shut the Node process down.

ng-reflect-* attributes are deprecated and no longer produced by default. Code and tests that relied on them need refactoring. For a smoother upgrade, provideNgReflectAttributes() (from @angular/core) restores the old behaviour in development mode — add it to the bootstrap providers as a temporary measure, not a permanent one.

Deprecated in v20 Replacement
ngIf / ngFor / ngSwitch @if / @for / @switch
All of @angular/platform-browser-dynamic Standalone bootstrapping with bootstrapApplication
HammerJS support Native pointer events
@angular/platform-server/testing End-to-end tests for SSR behaviour
Terminal window
ng update @angular/cli@20 @angular/core@20

ng update runs the schematics that ship with the release, including the migration away from InjectFlags. Before starting:

  1. Check your Node and TypeScript versions. Node 20.19+/22.12+/24.0+ and TypeScript 5.8+.
  2. Upgrade one major at a time. ng update is designed for single-major steps; skipping versions skips their migrations.
  3. Expect test failures around error handling. The rethrow-by-default change surfaces errors your tests were previously swallowing. Read each one before reaching for rethrowApplicationErrors: false.
  4. Grep for ng-reflect in tests and tooling.
  5. Grep templates for properties named in or void.
  6. Search for (foo?.bar).baz patterns — parenthesised expressions after a safe navigation.

Run the codemods separately, and commit between each:

Terminal window
ng generate @angular/core:control-flow
ng generate @angular/core:standalone
ng generate @angular/core:inject
ng generate @angular/core:signal-input-migration

A migration that produces a four-thousand-line diff is not reviewable as one commit.