Update angular monorepo to v20 (major)

v20.0.5

Compare Source

compiler-cli

core

router

upgrade

v20.0.4

Compare Source

core

migrations

v20.0.3

Compare Source

v20.0.2

Compare Source

core

v20.0.1

Compare Source

compiler

core

migrations

service-worker

v20.0.0

Compare Source

Blog post: https://blog.angular.dev/announcing-angular-v20-b5c9c06cf301

Breaking Changes

common

• 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.
• 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

• 'in' in an expression now refers to the operator

• 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

• TypeScript versions less than 5.8 are no longer supported.

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

• 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

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

• • 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.
• • TestBed.get has been removed. Use TestBed.inject instead.

• afterRender was renamed to afterEveryRender.

• • 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: https://angular.dev/reference/versions

• 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.

• 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.

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

• 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.

• 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.

• 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

• 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.
• 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.
• 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

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

platform-browser

• All entries of the @angular/platform-browser-dynamic
• HammerJS support is deprecated and will be removed in a future major version.

platform-server

• @angular/platform-server/testing

  Use e2e tests to verify SSR behavior instead.

common

compiler

compiler-cli

core

forms

http

platform-browser

platform-server

router

v19.2.14

Compare Source

compiler

migrations

v19.2.13

Compare Source

common

service-worker

v19.2.12

Compare Source

common

compiler

compiler-cli

core

platform-server

v19.2.11

Compare Source

v19.2.10

Compare Source

common

core

platform-server

v19.2.9

Compare Source

core

v19.2.8

Compare Source

forms

v19.2.7

Compare Source

common

core

http

v19.2.6

Compare Source

compiler

compiler-cli

core

language-service

v19.2.5

Compare Source

animations

compiler

compiler-cli

core

language-service

migrations

router

service-worker

v19.2.4

Compare Source

core

localize

platform-browser

v19.2.3

Compare Source

compiler-cli

core

platform-browser-dynamic

upgrade

v19.2.2

Compare Source

common

compiler

compiler-cli

core

platform-server

router

v19.2.1

Compare Source

compiler

migrations

v19.2.0

Compare Source

common

compiler

core

forms

migrations

platform-browser

platform-server

v19.1.8

Compare Source

benchpress

common

core

language-service

v19.1.7

Compare Source

common

compiler-cli

forms

v19.1.6

Compare Source

compiler

compiler-cli

core

migrations

v19.1.5

Compare Source

compiler-cli

v19.1.4

Compare Source

core

elements

platform-browser

router

service-worker

v19.1.3

Compare Source

compiler

compiler-cli

core

migrations

platform-browser

v19.1.2

Compare Source

compiler

compiler-cli

core

v19.1.1

Compare Source

core

platform-browser

v19.1.0

Compare Source

common

compiler

compiler-cli

core

migrations

platform-browser

router

v19.0.7

Compare Source

compiler-cli

core

migrations

v19.0.6

Compare Source

compiler-cli

core

platform-browser

router

v19.0.5

Compare Source

core

platform-server

v19.0.4

Compare Source

compiler-cli

core

platform-browser

v19.0.3

Compare Source

v19.0.2

Compare Source

compiler-cli

core

migrations

platform-server

v19.0.1

Compare Source

compiler-cli

core

forms

language-service

migrations

v19.0.0

Compare Source

Blog post: https://blog.angular.dev/meet-angular-v19-7b29dfd05b84

Breaking Changes

compiler

• this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..
• changes to CSS selectors parsing where introduced, mainly to: pseudo selectors :where() and :is(), parsing of :host and host-context, parsing selectors within pseudo selector arguments (for instance comma separated selectors). These changes could lead to a different specificity of the resulting selectors and/or previously broken selectors being applied now, for example :where(:host) used to transform to :where()[ng-host] and is being :where([ng-host]) now. Unlike the previous outcome, the new result can target elements and therefore could lead to breakages.

core

• Angular directives, components and pipes are now standalone by default.

  • Specify standalone: false for declarations that are currently declared in @NgModules.
  • ng update for v19 will take care of this automatically.

• TypeScript versions less than 5.5 are no longer supported.

• Timing changes for effect API (in developer preview):

  • effects which are triggered outside of change detection run as part of the change detection process instead of as a microtask. Depending on the specifics of application/test setup, this can result in them executing earlier or later (or requiring additional test steps to trigger; see below examples).

  • effects which are triggered during change detection (e.g. by input signals) run earlier, before the component's template.

• ExperimentalPendingTasks has been renamed to PendingTasks.

• The autoDetect feature of ComponentFixture will now attach the fixture to the ApplicationRef. As a result, errors during automatic change detection of the fixture be reported to the ErrorHandler. This change may cause custom error handlers to observe new failures that were previously unreported.

• createComponent will now render default fallback with empty projectableNodes.

  • When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.

  // The first ng-content will render the default fallback content if present
  createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
  
  // To prevent projecting the default fallback content:
  createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });
  

• Errors that are thrown during ApplicationRef.tick will now be rethrown when using TestBed. These errors should be resolved by ensuring the test environment is set up correctly to complete change detection successfully. There are two alternatives to catch the errors:

  • Instead of waiting for automatic change detection to happen, trigger it synchronously and expect the error. For example, a jasmine test could write expect(() => TestBed.inject(ApplicationRef).tick()).toThrow()
  • TestBed will reject any outstanding ComponentFixture.whenStable promises. A jasmine test, for example, could write expectAsync(fixture.whenStable()).toBeRejected().

  As a last resort, you can configure errors to not be rethrown by setting rethrowApplicationErrors to false in TestBed.configureTestingModule.

• The timers that are used for zone coalescing and hybrid mode scheduling (which schedules an application state synchronization when changes happen outside the Angular zone) will now run in the zone above Angular rather than the root zone. This will mostly affect tests which use fakeAsync: these timers will now be visible to fakeAsync and can be affected by tick or flush.

• The deprecated factories property in KeyValueDiffers has been removed.

elements

• as part of switching away from custom CD behavior to the hybrid scheduler, timing of change detection around custom elements has changed subtly. These changes make elements more efficient, but can cause tests which encoded assumptions about how or when elements would be checked to require updating.

localize

• The name option in the ng add @localize`` schematic has been removed in favor of the project option.

platform-browser

• The deprecated BrowserModule.withServerTransition method has been removed. Please use the APP_ID DI token to set the application id instead.

router

• The Router.errorHandler property has been removed. Adding an error handler should be configured in either withNavigationErrorHandler with provideRouter or the errorHandler property in the extra options of RouterModule.forRoot. In addition, the error handler cannot be used to change the return value of the router navigation promise or prevent it from rejecting. Instead, if you want to prevent the promise from rejecting, use resolveNavigationPromiseOnError.
• The return type of the Resolve interface now includes RedirectCommand.

common

compiler

compiler-cli

core

elements

forms

http

language-service

localize

migrations

platform-browser

platform-server

router

service-worker

v18.2.13

Compare Source

migrations

v18.2.12

Compare Source

compiler-cli

v18.2.11

Compare Source

core

v18.2.10

Compare Source

compiler

localize

v18.2.9

Compare Source

compiler-cli

v18.2.8

Compare Source

compiler

compiler-cli

core

platform-server

v18.2.7

Compare Source

common

compiler-cli

core

http

migrations

upgrade

v18.2.6

Compare Source

v18.2.5

Compare Source

compiler-cli

core

migrations

v18.2.4

Compare Source

compiler

migrations

v18.2.3

Compare Source

http

v18.2.2

Compare Source

core

http

router

upgrade

v18.2.1

Compare Source

migrations

v18.2.0

Compare Source

compiler

compiler-cli

core

language-service

migrations

router

v18.1.5

Compare Source

compiler-cli

core

v18.1.4

Compare Source

compiler

compiler-cli

language-service

v18.1.3

Compare Source

compiler

compiler-cli

core

v18.1.2

Compare Source

compiler

compiler-cli

core

v18.1.1

Compare Source

common

compiler

compiler-cli

core

migrations

v18.1.0

Compare Source

common

compiler

compiler-cli

core

forms

http

language-service

router

v18.0.7

Compare Source

compiler

http

migrations

v18.0.6

Compare Source

common

core

router

v18.0.5

Compare Source

core

v18.0.4

Compare Source

compiler-cli

core

router

v18.0.3

Compare Source

benchpress

core

localize

migrations

v18.0.2

Compare Source

core

migrations

v18.0.1

Compare Source

compiler

compiler-cli

core

migrations

v18.0.0

Compare Source

Blog post "Angular v18 is now available".

Breaking Changes

animations

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

common

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

compiler

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

compiler-cli

• • Angular no longer supports TypeScript versions older than 5.4.

core

• 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.

• 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.

• 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.

• 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.

• 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.

• async has been removed, use waitForAsync instead.

• 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.

• 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.

• 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.

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

http

• 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 StateKey, TransferState and makeStateKey have been removed from @angular/platform-browser, use the same APIs from @angular/core.

platform-browser-dynamic

• No longer used RESOURCE_CACHE_PROVIDER APIs have been removed.

platform-server

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

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

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

• 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

• 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.
• 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.
• 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.
• 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.
• 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

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

core

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

http

• HttpClientModule, HttpClientXsrfModule and HttpClientJsonpModule

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

animations

common

compiler

compiler-cli

core

forms

http

language-service

migrations

platform-browser

platform-browser-dynamic

platform-server

router

service-worker