@angular/platform-browser-dynamic

Blog post: blog.angular.dev/announcing-angular-v20-b5c9c06…

common

compiler

compiler-cli

core

forms

http

platform-browser

platform-server

router

Breaking Changes

common

• breaking

  Using the Y formatter (week-numbering year) without also including w (week number) is now detected as suspicious date pattern, as y is typically intended.

• breaking

  AsyncPipe now directly catches unhandled errors in
  subscriptions and promises and reports them to the application's
  ErrorHandler. For Zone-based applications, these errors would have
  been caught by ZoneJS and reported to ErrorHandler so the result is
  generally the same. The change to the exact mechanism for reporting can
  result in differences in test environments that will require test
  updates.

compiler

• breaking

  'in' in an expression now refers to the operator

• breaking

  void in an expression now refers to the operator

  Previously an expression in the template like {{void}} referred to a
  property on the component class. After this change it now refers to the
  void operator, which would make the above example invalid. If you have
  existing expressions that need to refer to a property named void,
  change the expression to use this.void instead: {{this.void}}.

core

• breaking

  • TypeScript versions less than 5.8 are no longer supported.

• breaking

  The TestBed.flushEffects() was removed - use
  the TestBed.tick() instead.

• breaking

  provideExperimentalCheckNoChangesForDebug has several
  breaking changes:

  • It is renamed to provideCheckNoChangesConfig

  • The behavior applies to all checkNoChanges runs

  • The useNgZoneOnStable option is removed. This wasn't found to be generally
    more useful than interval

• breaking

  provideExperimentalZonelessChangeDetection is
  renamed to provideZonelessChangeDetection as it is now "Developer
  Preview" rather than "Experimental".

• breaking

  • InjectFlags has been removed.

  • inject no longer accepts InjectFlags.

  • Injector.get no longer accepts InjectFlags.

  • EnvironmentInjector.get no longer accepts InjectFlags.

  • TestBed.get no longer accepts InjectFlags.

  • TestBed.inject no longer accepts InjectFlags.

• breaking

  • TestBed.get has been removed. Use TestBed.inject instead.

• breaking

  afterRender was renamed to afterEveryRender.

• breaking

  Angular no longer supports Node.js v18.

  • Node.js versions 22.0 to 22.10 are also no longer supported.

  Before upgrading to Angular v20, ensure the Node.js version is at least 20.11.1.
  For the full list of supported versions, visit: angular.dev/reference/versions

• breaking

  PendingTasks.run no longer returns the result of the
  async function. If this behavior is desired, it can be re-implemented
  manually with the PendingTasks.add. Be aware, however, that promise rejections
  will need to be handled or they can cause the node process to shut down
  when using SSR.

• breaking

  Uncaught errors in listeners which were previously only reported to
  ErrorHandler are now also reported to Angular's internal error
  handling machinery. For tests, this means that the error will be
  rethrown by default rather than only logging the error. Developers
  should fix these errors, catch them in the test if the test is
  intentionally covering an error case, or use rethrowApplicationErrors: false in configureTestingModule as a last resort.

• breaking

  The any overload has been removed from
  injector.get. It now only supports ProviderToken<T> and (deprecated
  since v4) string.

• breaking

  Animations are guaranteed to be flushed when Angular
  runs automatic change detection or manual calls to ApplicationRef.tick.
  Prior to this change, animations would not be flushed in some situations
  if change detection did not run on any views attached to the
  application. This change can affect tests which may rely on the old
  behavior, often by making assertions on DOM elements that should have
  been removed but weren't because DOM removal is delayed until animations
  are flushed.

• breaking

  ApplicationRef.tick will no longer catch and report
  errors to the appplication ErrorHandler. Errors will instead be thrown out of
  the method and will allow callers to determine how to handle these
  errors, such as aborting follow-up work or reporting the error and
  continuing.

• breaking

  This commit deprecates ng-reflect-* attributes and updates the runtime to stop producing them by default. Please refactor application and test code to avoid relying on ng-reflect-* attributes.

  To enable a more seamless upgrade to v20, we've added the provideNgReflectAttributes() function (can be imported from the @angular/core package), which enables the mode in which Angular would be producing those attribites (in dev mode only). You can add the provideNgReflectAttributes() function to the list of providers within the bootstrap call.

router

• breaking

  The RedirectFn can now return Observable or
  Promise. Any code that directly calls functions returning this type
  may need to be adjusted to account for this.

• breaking

  Several methods in the public API of the Router which
  required writable arrays have now been updated to accept readonly
  arrays when no mutations are done.

• breaking

  The guards arrays on Route no longer include any in
  the type union. The union includes functions for the functional guards
  as well as a type matching Injector.get: ProviderToken<T>|string.
  Note that string is still deprecated on both the route guards and
  Injector.get.

Deprecations

core

• deprecated

  ngIf/ngFor/ngSwitch are deprecated. Use the control flow blocks instead (@for/@if/@switch).

platform-browser

• deprecated

  All entries of the @angular/platform-browser-dynamic

• deprecated

  HammerJS support is deprecated and will be removed in a future major version.

platform-server

• deprecated

  @angular/platform-server/testing

  Use e2e tests to verify SSR behavior instead.