@angular/upgrade

animations

common

compiler

compiler-cli

core

forms

http

language-service

migrations

platform-browser

platform-browser-dynamic

platform-server

router

service-worker

Breaking Changes

animations

• deprecated

  Deprecated matchesElement method has been removed from AnimationDriver as it is unused.

common

• breaking

  The deprecated isPlatformWorkerUi and isPlatformWorkerApp have been removed without replacement, as they serve no purpose since the removal of the WebWorker platform.

compiler

• breaking

  Angular only supports writable expressions inside of two-way bindings.

compiler-cli

• breaking

  • Angular no longer supports TypeScript versions older than 5.4.

core

• breaking

  OnPush views at the root of the application need to
  be marked dirty for their host bindings to refresh. Previously, the host
  bindings were refreshed for all root views without respecting the
  OnPush change detection strategy.

• breaking

  OnPush views at the root of the application need to
  be marked dirty for their host bindings to refresh. Previously, the host
  bindings were refreshed for all root views without respecting the
  OnPush change detection strategy.

• breaking

  The ComponentFixture autoDetect feature will no
  longer refresh the component's host view when the component is OnPush
  and not marked dirty. This exposes existing issues in components which
  claim to be OnPush but do not correctly call markForCheck when they
  need to be refreshed. If this change causes test failures, the easiest
  fix is to change the component to ChangeDetectionStrategy.Default.

• breaking

  ComponentFixture.whenStable now matches the
  ApplicationRef.isStable observable. Prior to this change, stability
  of the fixture did not include everything that was considered in
  ApplicationRef. whenStable of the fixture will now include unfinished
  router navigations and unfinished HttpClient requests. This will cause
  tests that await the whenStable promise to time out when there are
  incomplete requests. To fix this, remove the whenStable,
  instead wait for another condition, or ensure HttpTestingController
  mocks responses for all requests. Try adding HttpTestingController.verify()
  before your await fixture.whenStable to identify the open requests.
  Also, make sure your tests wait for the stability promise. We found many
  examples of tests that did not, meaning the expectations did not execute
  within the test body.

  In addition, ComponentFixture.isStable would synchronously switch to
  true in some scenarios but will now always be asynchronous.

• breaking

  Angular will ensure change detection runs, even when the state update originates from
  outside the zone, tests may observe additional rounds of change
  detection compared to the previous behavior.

  This change will be more likely to impact existing unit tests.
  This should usually be seen as more correct and the test should be updated,
  but in cases where it is too much effort to debug, the test can revert to the old behavior by adding
  provideZoneChangeDetection({schedulingMode: NgZoneSchedulingMode.NgZoneOnly})
  to the TestBed providers.

  Similarly, applications which may want to update state outside the zone
  and not trigger change detection can add
  provideZoneChangeDetection({schedulingMode: NgZoneSchedulingMode.NgZoneOnly})
  to the providers in bootstrapApplication or add
  schedulingMode: NgZoneSchedulingMode.NgZoneOnly to the
  BootstrapOptions of bootstrapModule.

• breaking

  When Angular runs change detection, it will continue to
  refresh any views attached to ApplicationRef that are still marked for
  check after one round completes. In rare cases, this can result in infinite
  loops when certain patterns continue to mark views for check using
  ChangeDetectorRef.detectChanges. This will be surfaced as a runtime
  error with the NG0103 code.

• breaking

  async has been removed, use waitForAsync instead.

• breaking

  The ComponentFixture.autoDetect feature now executes
  change detection for the fixture within ApplicationRef.tick. This more
  closely matches the behavior of how a component would refresh in
  production. The order of component refresh in tests may be slightly
  affected as a result, especially when dealing with additional components
  attached to the application, such as dialogs. Tests sensitive to this
  type of change (such as screenshot tests) may need to be updated.
  Concretely, this change means that the component will refresh before
  additional views attached to ApplicationRef (i.e. dialog components).
  Prior to this change, the fixture component would refresh after other
  views attached to the application.

• breaking

  The exact timing of change detection execution when
  using event or run coalescing with NgZone is now the first of either
  setTimeout or requestAnimationFrame. Code which relies on this
  timing (usually by accident) will need to be adjusted. If a callback
  needs to execute after change detection, we recommend afterNextRender
  instead of something like setTimeout.

• breaking

  Newly created and views marked for check and reattached
  during change detection are now guaranteed to be refreshed in that same
  change detection cycle. Previously, if they were attached at a location
  in the view tree that was already checked, they would either throw
  ExpressionChangedAfterItHasBeenCheckedError or not be refreshed until
  some future round of change detection. In rare circumstances, this
  correction can cause issues. We identified one instance that relied on
  the previous behavior by reading a value on initialization which was
  queued to be updated in a microtask instead of being available in the
  current change detection round. The component only read this value during
  initialization and did not read it again after the microtask updated it.

• breaking

  Testability methods increasePendingRequestCount,
  decreasePendingRequestCount and getPendingRequestCount have been
  removed. This information is tracked with zones.

http

• breaking

  By default we now prevent caching of HTTP requests that require authorization . To opt-out from this behaviour use the includeRequestsWithAuthHeaders option in withHttpTransferCache.

  Example:

  withHttpTransferCache({
    includeRequestsWithAuthHeaders: true,
  })

platform-browser

• deprecated

  Deprecated StateKey, TransferState and makeStateKey have been removed from @angular/platform-browser, use the same APIs from @angular/core.

platform-browser-dynamic

• breaking

  No longer used RESOURCE_CACHE_PROVIDER APIs have been removed.

platform-server

• deprecated

  Deprecated platformDynamicServer has been removed. Add an import @angular/compiler and replace the usage with platformServer

• deprecated

  Deprecated ServerTransferStateModule has been removed. TransferState can be use without providing this module.

• deprecated

  Deprecated useAbsoluteUrl and baseUrl been removed from PlatformConfig. Provide and absolute url instead.

• breaking

  Legacy handling or Node.js URL parsing has been removed from ServerPlatformLocation.

  The main differences are;

  • pathname is always suffixed with a /.

  • port is empty when http: protocol and port in url is 80

  • port is empty when https: protocol and port in url is 443

router

• breaking

  Guards can now return RedirectCommand for redirects
  in addition to UrlTree. Code which expects only boolean or UrlTree
  values in Route types will need to be adjusted.

• breaking

  This change allows Route.redirectTo to be a function
  in addition to the previous string. Code which expects redirectTo to
  only be a string on Route objects will need to be adjusted.

• breaking

  When a a guard returns a UrlTree as a redirect, the
  redirecting navigation will now use replaceUrl if the initial
  navigation was also using the replaceUrl option. If this is not
  desirable, the redirect can configure new NavigationBehaviorOptions by
  returning a RedirectCommand with the desired options instead of UrlTree.

• breaking

  Providers available to the routed components always
  come from the injector heirarchy of the routes and never inherit from
  the RouterOutlet. This means that providers available only to the
  component that defines the RouterOutlet will no longer be available to
  route components in any circumstances. This was already the case
  whenever routes defined providers, either through lazy loading an
  NgModule or through explicit providers on the route config.

• breaking

  Providers available to the routed components always
  come from the injector heirarchy of the routes and never inherit from
  the RouterOutlet. This means that providers available only to the
  component that defines the RouterOutlet will no longer be available to
  route components in any circumstances. This was already the case
  whenever routes defined providers, either through lazy loading an
  NgModule or through explicit providers on the route config.

Deprecations

common

• deprecated

  getCurrencySymbol, getLocaleCurrencyCode, getLocaleCurrencyName, getLocaleCurrencySymbol, getLocaleDateFormat, getLocaleDateTimeFormat, getLocaleDayNames, getLocaleDayPeriods, getLocaleDirection, getLocaleEraNames, getLocaleExtraDayPeriodRules, getLocaleExtraDayPeriods, getLocaleFirstDayOfWeek, getLocaleId, getLocaleMonthNames, getLocaleNumberFormat, getLocaleNumberSymbol, getLocalePluralCase, getLocaleTimeFormat, getLocaleWeekEndRange, getNumberOfCurrencyDigits

core

• deprecated

  @Component.interpolation is deprecated. Use Angular's
  delimiters instead.

http

• deprecated

  HttpClientModule, HttpClientXsrfModule and HttpClientJsonpModule

  As mentionned, those modules can be replaced by provider function only.