16.0.0 (2023-05-03)

Commit	Description
	remove Angular Compatibility Compiler (ngcc) (#49101)
	remove deprecated EventManager method addGlobalEventListener (#49645)

common

Commit	Description
	Provide MockPlatformLocation by default in BrowserTestingModule (#49137)
	strict type checking for ngtemplateoutlet (#48374)
	remove deprecated XhrFactory export from http entrypoint (#49251)

compiler

Commit	Description
	add support for compile-time required inputs (#49304)
	add support for compile-time required inputs (#49453)
	add support for compile-time required inputs (#49468)
	drop support for TypeScript 4.8 (#49155)
	support multiple configuration files in extends (#49125)
	incorrectly matching directives on attribute bindings (#49713)
	Produce diagnositc if directive used in host binding is not exported (#49527)

compiler-cli

Commit	Description
	Add an extended diagnostic for nSkipHydration (#49512)
	Catch FatalDiagnosticError during template type checking (#49527)
	optimize NgModule emit for standalone components (#49837)

core

Commit	Description
	add assertInInjectionContext (#49529)
	add mergeApplicationConfig method (#49253)
	Add ability to configure NgZone in bootstrapApplication (#49557)
	add Angular Signals to the public API (#49150)
	add API to provide CSP nonce for inline stylesheets (#49444)
	add migration to remove moduleId references (#49496)
	add support for TypeScript 5.0 (#49126)
	allow removal of previously registered DestroyRef callbacks (#49493)
	Allow typeguards on QueryList.filter (#48042)
	Drop public factories property for IterableDiffers : Breaking change (#49598)
	drop support for zone.js versions <=0.12.0 (#49331)
	effects can optionally return a cleanup function (#49625)
	expose makeStateKey, StateKey and TransferState (#49563)
	expose onDestroy on ApplicationRef (#49677)
	implement takeUntilDestroyed in rxjs-interop (#49154)
	introduce runInInjectionContext and deprecate prior version (#49396)
	introduce concept of DestroyRef (#49158)
	Mark components for check if they read a signal (#49153)
	prototype implementation of @angular/core/rxjs-interop (#49154)
	remove entryComponents (#49484)
	support usage of non-experimental decorators with TypeScript 5.0 (#49492)
	add newline to hydration mismatch error (#49965)
	allow async functions in effects (#49783)
	catch errors from source signals outside of .next (#49769)
	ComponentRef.setInput only sets input when not equal to previous (#49607)
	deprecate moduleId @Component property (#49496)
	Ensure effects can be created when Zone is not defined (#49890)
	ensure takeUntilDestroyed unregisters onDestroy listener on unsubscribe (#49901)
	error if document body is null (#49818)
	execute input setters in non-reactive context (#49906)
	execute query setters in non-reactive context (#49906)
	execute template creation in non-reactive context (#49883)
	Fix capitalization of toObservableOptions (#49832)
	generate consistent component IDs (#48253)
	include inner ViewContainerRef anchor nodes into ViewRef.rootNodes output (#49867)
	make sure that lifecycle hooks are not tracked (#49701)
	onDestroy should be registered only on valid DestroyRef (#49804)
	resolve InitialRenderPendingTasks promise on complete (#49784)
	toObservable should allow writes to signals in the effect (#49769)
	typing of TestBed Common token. (#49997)
	When using setInput, mark view dirty in same was as markForCheck (#49711)
	change RendererType2.styles to accept a only a flat array (#49072)
	generate a static application ID (#49422)
	Remove ReflectiveInjector symbol (#48103)
	remove Node.js v14 support (#49255)

forms

Commit	Description
	Improve typings form (async)Validators (#48679)

http

Commit	Description
	allow HttpClient to cache requests (#49509)
	delay accessing pendingTasks.whenAllTasksComplete (#49784)
	ensure new cache state is returned on each request (#49749)
	force macro task creation during HTTP request (#49546)
	HTTP cache was being disabled prematurely (#49826)
	wait for all XHR requests to finish before stabilizing application (#49776)

migrations

Commit	Description
	Migration to remove Router guard and resolver interfaces (#49337)

platform-browser

Commit	Description
	add a public API function to enable non-destructive hydration (#49666)
	deprecate withServerTransition call (#49422)
	enable HTTP request caching when using provideClientHydration (#49699)
	export deprecated TransferState as type (#50015)
	KeyEventsPlugin should keep the same behavior (#49330)
	only add ng-app-id to style on server side (#49465)
	reuse server generated component styles (#48253)
	set nonce attribute in a platform compatible way (#49624)
	move ApplicationConfig to core (#49253)
	remove deprecated BrowserTransferStateModule symbol (#49718)

platform-server

Commit	Description
	renderApplication now accepts a bootstrapping method (#49248)
	add provideServerSupport function to provide server capabilities to an application (#49380)
	rename provideServerSupport to provideServerRendering (#49678)
	bundle @angular/domino in via esbuild (#49229)
	remove dependency on @angular/platform-browser-dynamic (#50064)
	deprecate useAbsoluteUrl and baseUrl (#49546)
	remove renderApplication overload that accepts a component (#49463)
	remove deprecated renderModuleFactory (#49247)

router

Commit	Description
	Expose information about the last successful Navigation (#49235)
	helper functions to convert class guards to functional (#48709)
	Opt-in for binding Router information to component inputs (#49633)
	Ensure anchor scrolling happens on ignored same URL navigations (#48025)
	fix = not parsed in router segment name (#47332)
	Remove deprecated ComponentFactoryResolver from APIs (#49239)
	remove RouterEvent from Event union type (#46061)
	Route matching should only happen once when navigating (#49163)
	Route matching should only happen once when navigating (#49163)
	Router.createUrlTree should work with any ActivatedRoute (#48508)

service-worker

Commit	Description
	add function to provide service worker (#48247)

Breaking Changes

• Angular Compatibility Compiler (ngcc) has been removed and as a result Angular View Engine libraries will no longer work
• Deprecated EventManager method addGlobalEventListener has been removed as it is not used by Ivy.

bazel

• Several changes to the Angular Package Format (APF)
  • Removal of FESM2015
  • Replacing ES2020 with ES2022
  • Replacing FESM2020 with FESM2022
• Several changes to the Angular Package Format (APF)
  • Removal of FESM2015
  • Replacing ES2020 with ES2022
  • Replacing FESM2020 with FESM2022

common

• MockPlatformLocation is now provided by default in tests.
  Existing tests may have behaviors which rely on
  BrowserPlatformLocation instead. For example, direct access to the
  window.history in either the test or the component rather than going
  through the Angular APIs (Location.getState()). The quickest fix is to
  update the providers in the test suite to override the provider again
  TestBed.configureTestingModule({providers: [{provide: PlatformLocation, useClass: BrowserPlatformLocation}]}).
  The ideal fix would be to update the code to instead be compatible with
  MockPlatformLocation instead.
• If the 'ngTemplateOutletContext' is different from the context, it will result in a compile-time error.

Before the change, the following template was compiling:

interface MyContext {
  $implicit: string;
}

@Component({
  standalone: true,
  imports: [NgTemplateOutlet],
  selector: 'person',
  template: `
    <ng-container
      *ngTemplateOutlet="
        myTemplateRef;
        context: { $implicit: 'test', xxx: 'xxx' }
      "></ng-container>
  `,
})
export class PersonComponent {
  myTemplateRef!: TemplateRef<MyContext>;
}

However, it does not compile now because the 'xxx' property does not exist in 'MyContext', resulting in the error: 'Type '{ $implicit: string; xxx: string; }' is not assignable to type 'MyContext'.'

The solution is either:

• add the 'xxx' property to 'MyContext' with the correct type or
• add '$any(...)' inside the template to make the error disappear. However, adding '$any(...)' does not correct the error but only preserves the previous behavior of the code.
• Deprecated XhrFactory export from @angular/common/http has been removed. Use XhrFactory from @angular/common instead.

compiler

• • TypeScript 4.8 is no longer supported.

core

• QueryList.filter now supports type guard functions, which will result in type narrowing. Previously if you used type guard functions, it resulted in no changes to the return type. Now the type would be narrowed, which might require updates to the application code that relied on the old behavior.

• zone.js versions 0.11.x and 0.12.x are not longer supported.

• • entryComponents has been deleted from the @NgModule and @Component public APIs. Any usages can be removed since they weren't doing anyting.
  • ANALYZE_FOR_ENTRY_COMPONENTS injection token has been deleted. Any references can be removed.

• ComponentRef.setInput will only set the input on the
  component if it is different from the previous value (based on Object.is
  equality). If code relies on the input always being set, it should be
  updated to copy objects or wrap primitives in order to ensure the input
  value differs from the previous call to setInput.

• RendererType2.styles no longer accepts a nested arrays.

• The APP_ID token value is no longer randomly generated. If you are bootstrapping multiple application on the same page you will need to set to provide the APP_ID yourself.

  bootstrapApplication(ComponentA, {
    providers: [
     { provide: APP_ID, useValue: 'app-a' },
     // ... other providers ...
    ]
  });

• The ReflectiveInjector and related symbols were removed. Please update the code to avoid references to the ReflectiveInjector symbol. Use Injector.create as a replacement to create an injector instead.

• Node.js v14 support has been removed

  Node.js v14 is planned to be End-of-Life on 2023-04-30. Angular will stop supporting Node.js v14 in Angular v16. Angular v16 will continue to officially support Node.js versions v16 and v18.

platform-browser

• The deprecated BrowserTransferStateModule was removed, since it's no longer needed. The TransferState class can be injected without providing the module. The BrowserTransferStateModule was empty starting from v14 and you can just remove the reference to that module from your applications.

platform-server

• Users that are using SSR with JIT mode will now need to add import to @angular/compiler before bootstrapping the application.

  NOTE: this does not effect users using the Angular CLI.

• renderApplication method no longer accepts a root component as first argument. Instead, provide a bootstrapping function that returns a Promise<ApplicationRef>.

  Before

  const output: string = await renderApplication(RootComponent, options);

  Now

  const bootstrap = () => bootstrapApplication(RootComponent, appConfig);
  const output: string = await renderApplication(bootstrap, options);

• renderModuleFactory has been removed. Use renderModule instead.

router

• The Scroll event's routerEvent property may also be
  a NavigationSkipped event. Previously, it was only a NavigationEnd
  event.
• ComponentFactoryResolver has been removed from Router APIs.
  Component factories are not required to create an instance of a component
  dynamically. Passing a factory resolver via resolver argument is no longer needed
  and code can instead use ViewContainerRef.createComponent without the
  factory resolver.
• The RouterEvent type is no longer present in the Event union type representing all router event types. If you have code using something like filter((e: Event): e is RouterEvent => e instanceof RouterEvent), you'll need to update it to filter((e: Event|RouterEvent): e is RouterEvent => e instanceof RouterEvent).
• Tests which mock ActivatedRoute instances may need to be adjusted
  because Router.createUrlTree now does the right thing in more
  scenarios. This means that tests with invalid/incomplete ActivatedRoute mocks
  may behave differently than before. Additionally, tests may now navigate
  to a real URL where before they would navigate to the root. Ensure that
  tests provide expected routes to match.
  There is rarely production impact, but it has been found that relative
  navigations when using an ActivatedRoute that does not appear in the
  current router state were effectively ignored in the past. By creating
  the correct URLs, this sometimes resulted in different navigation
  behavior in the application. Most often, this happens when attempting to
  create a navigation that only updates query params using an empty
  command array, for example router.navigate([], {relativeTo: route, queryParams: newQueryParams}). In this case, the relativeTo property
  should be removed.

Deprecations

core

• makeStateKey, StateKey and TransferState exports have been moved from @angular/platform-browser to @angular/core. Please update the imports.

- import {makeStateKey, StateKey, TransferState} from '@angular/platform-browser';
+ import {makeStateKey, StateKey, TransferState} from '@angular/core';

• EnvironmentInjector.runInContext is now deprecated, with
  runInInjectionContext functioning as a direct replacement:

  // Previous method version (deprecated):
  envInjector.runInContext(fn);
  // New standalone function:
  runInInjectionContext(envInjector, fn);

• The @Directive/@Component moduleId property is now
  deprecated. It did not have any effect for multiple major versions and
  will be removed in v17.

platform-browser

• BrowserModule.withServerTransition has been deprecated. APP_ID should be used instead to set the application ID.
  NB: Unless, you render multiple Angular applications on the same page, setting an application ID is not necessary.

  Before:

  imports: [
    BrowserModule.withServerTransition({ appId: 'serverApp' }),
    ...
  ]

  After:

  imports: [
    BrowserModule,
    { provide: APP_ID, useValue: 'serverApp' },
    ...
  ],

• ApplicationConfig has moved, please import ApplicationConfig from @angular/core instead.

platform-server

• PlatformConfig.baseUrl and PlatformConfig.useAbsoluteUrl platform-server config options are deprecated as these were not used.