v13.0.0

Compare Source

Breaking Changes

@​angular/cli

• We drop support for Node.js versions prior to 12.20.

@​schematics/angular

• classlist.js and web-animations-js are removed from application polyfills and uninstalled from the package. These were only needed for compatibility with Internet Explorer, which is no longer needed now that Angular only supports evergreen browsers. See: https://angular.io/guide/browser-support.

Add the following to the polyfills file for an app to re-add these packages:

import 'classlist.js';
import 'web-animations-js';

And then run:

npm install classlist.js web-animations-js --save

• We removed several deprecated @schematics/angular deprecated options.
• lintFix have been removed from all schematics. ng lint --fix should be used instead.
• legacyBrowsers have been removed from the application schematics since IE 11 is no longer supported.
• configuration has been removed from the web-worker as it was unused.
• target has been removed from the service-worker as it was unused.

@​angular-devkit/build-angular

• Support for karma-coverage-instanbul-reporter has been dropped in favor of the official karma coverage plugin karma-coverage.

• Support for node-sass has been removed. sass will be used by default to compile SASS and SCSS files.

• NG_PERSISTENT_BUILD_CACHE environment variable option no longer have effect. Configure cli.cache in the workspace configuration instead.

{
  "$schema": "./node_modules/@​angular/cli/lib/config/schema.json",
  "version": 1,
  "cli": {
    "cache": {
      "enabled": true,
      "path": ".custom-cache-path",
      "environment": "all"
    }
  }
  ...
}

• The automatic inclusion of Angular-required ES2015 polyfills to support ES5 browsers has been removed. Previously when targetting ES5 within the application's TypeScript configuration or listing an ES5 requiring browser in the browserslist file, Angular-required polyfills were included in the built application. However, with Angular no longer supporting IE11, there are now no browsers officially supported by Angular that would require these polyfills. As a result, the automatic inclusion of these ES2015 polyfills has been removed. Any polyfills manually added to an application's code are not affected by this change.

• With this change a number of deprecated dev-server builder options which proxied to the browser builder have been removed. These options should be configured in the browser builder instead.

The removed options are:

• aot

• sourceMap

• deployUrl

• baseHref

• vendorChunk

• commonChunk

• optimization

• progress

• With this change we removed several deprecated builder options

• extractCss has been removed from the browser builder. CSS is now always extracted.

• servePathDefaultWarning and hmrWarning have been removed from the dev-server builder. These options had no effect.

• Deprecated @angular-devkit/build-angular:tslint builder has been removed. Use https://github.com/angular-eslint/angular-eslint instead.

• Differential loading support has been removed. With Angular no longer supporting IE11, there are now no browsers officially supported by Angular that require ES5 code. As a result, differential loading's functionality for creating and conditionally loading ES5 and ES2015+ variants of an application is no longer required.

• TypeScript versions prior to 4.4 are no longer supported.

• The dev-server now uses WebSockets to communicate changes to the browser during HMR and live-reloaded. If during your development you are using a proxy you will need to enable proxying of WebSockets.

• We remove inlining of Google fonts in WOFF format since IE 11 is no longer supported. Other supported browsers use WOFF2.

@​angular-devkit/build-webpack

• Support for webpack-dev-server version 3 has been removed. For more information about the migration please see: https://github.com/webpack/webpack-dev-server/blob/master/migration-v4.md

Note: this change only affects users depending on @angular-devkit/build-webpack directly.

@​angular-devkit/core

• With this change we drop support for the deprecated behaviour to transform id in schemas. Use $id instead.

Note: this only effects schematics and builders authors.

• The deprecated JSON parser has been removed from public API. jsonc-parser should be used instead.

@​angular-devkit/schematics

• isAction has been removed without replacement as it was unused.

• With this change we remove the following deprecated APIs

• TslintFixTask

• TslintFixTaskOptions

Note: this only effects schematics developers.

@​ngtools/webpack

• Deprecated inlineStyleMimeType option has been removed from AngularWebpackPluginOptions. Use inlineStyleFileExtension instead.

• Applications directly using the webpack-cli and not the Angular CLI to build must set the environment variable DISABLE_V8_COMPILE_CACHE=1. The @ngtools/webpack package now uses dynamic imports to provide support for the ESM @angular/compiler-cli package. The v8-compile-cache package used by the webpack-cli does not currently support dynamic import expressions and will cause builds to fail if the environment variable is not specified. Applications using the Angular CLI are not affected by this limitation.

Deprecations

• @angular-devkit/build-optimizer

It's functionality has been included in @angular-devkit/build-angular so this package is no longer needed by the CLI and we will stop publishing the package soon. It has been an experimental (never hit 1.0.0) and internal (only used by Angular itself) package and should be not be used directly by others.

@​angular-devkit/build-angular

• NG_BUILD_CACHE environment variable option will be removed in the next major version. Configure cli.cache in the workspace configuration instead.

@​angular/cli

@​schematics/angular

@​angular-devkit/architect

@​angular-devkit/build-angular

@​angular-devkit/build-webpack

@​angular-devkit/core

@​angular-devkit/schematics

@​ngtools/webpack

Special Thanks

Alan Agius, Charles Lyding, Doug Parker, Douglas Parker, Joey Perrott, Kristiyan Kostadinov, Lukas Spirig and Paul Gschwendtner

v13.0.0

Compare Source

Breaking Changes

common

• The behavior of the SpyLocation used by the RouterTestingModule has changed
  to match the behavior of browsers. It no longer emits a 'popstate' event
  when Location.go is called. In addition, simulateHashChange now
  triggers both a hashchange and a popstate event.
  Tests which use location.go and expect the changes to be picked up by
  the Router should likely change to simulateHashChange instead.
  Each test is different in what it attempts to assert so there is no
  single change that works for all tests. Each test using the SpyLocation to
  simulate browser URL changes should be evaluated on a case-by-case basis.

core

• TypeScript versions older than 4.4.2 are no longer supported.

• NodeJS versions older than v12.20.0 are no longer
  supported due to the Angular packages using the NodeJS package exports
  feature with subpath patterns.

• The WrappedValue class can no longer be imported from @angular/core,
  which may result in compile errors or failures at runtime if outdated
  libraries are used that are still using WrappedValue. The usage of
  WrappedValue should be removed as no replacement is available.

forms

• A new type called FormControlStatus has been introduced, which is a union of all possible status strings for form controls. AbstractControl.status has been narrowed from string to FormControlStatus, and statusChanges has been narrowed from Observable<any> to Observable<FormControlStatus>. Most applications should consume the new types seamlessly. Any breakage caused by this change is likely due to one of the following two problems: (1) the app is comparing AbstractControl.status against a string which is not a valid status; or, (2) the app is using statusChanges events as if they were something other than strings.

router

• The default url serializer would previously drop
  everything after and including a question mark in query parameters. That
  is, for a navigation to /path?q=hello?&other=123, the query
  params would be parsed to just {q: 'hello'}. This is
  incorrect because the URI spec allows for question mark characers in
  query data. This change will now correctly parse the params for the
  above example to be {v: 'hello?', other: '123'}.

• Previously null and undefined inputs for routerLink were
  equaivalent to empty string and there was no way to disable the link's
  navigation.
  In addition, the href is changed from a property HostBinding() to an
  attribute binding (HostBinding('attr.href')). The effect of this
  change is that DebugElement.properties['href'] will now return the
  href value returned by the native element which will be the full URL
  rather than the internal value of the RouterLink href property.

• The router will no longer replace the browser URL when a new navigation
  cancels an ongoing navigation. This often causes URL flicker and was
  only in place to support some AngularJS hybrid applications. Hybrid
  applications which rely on the navigationId being present on initial
  navigations that were handled by the Angular router should instead
  subscribe to NavigationCancel events and perform the
  location.replaceState themselves to add navigationId to the Router
  state.
  In addition, tests which assert urlChanges on the SpyLocation may
  need to be adjusted to account for the replaceState which is no longer
  triggered.

• It is no longer possible to use Route.loadChildren using a string
  value. The following supporting classes were removed from
  @angular/core:

• NgModuleFactoryLoader

• SystemJsNgModuleFactoryLoader

The @angular/router package no longer exports these symbols:

• SpyNgModuleFactoryLoader
• DeprecatedLoadChildren

The signature of the setupTestingRouter function from
@angular/core/testing has been changed to drop its NgModuleFactoryLoader
parameter, as an argument for that parameter can no longer be created.

service-worker

• The return type of SwUpdate#activateUpdate and SwUpdate#checkForUpdate changed to Promise<boolean>.

Although unlikely, it is possible that this change will cause TypeScript type-checking to fail in
some cases. If necessary, update your types to account for the new
return type.

Deprecations

• The renderModuleFactory symbol in @angular/platform-server is no longer necessary as of Angular v13.

The renderModuleFactory calls can be replaced with renderModule.

service-worker

• The SwUpdate#activated observable is deprecated.

The SwUpdate#activated observable only emits values as a direct response to calling
SwUpdate#activateUpdate() and was only useful for determining whether the call resulted in an
update or not. Now, the return value of SwUpdate#activateUpdate() can be used to determine the
outcome of the operation and therefore using SwUpdate#activated does not offer any benefit.

• The SwUpdate#availalbe observable is deprecated.

The new SwUpdate#versionUpdates observable provides the same information and more. Therefore, it
is possible to rebuild the same behavior as SwUpdate#availalbe using the events emitted by
SwUpdate#versionUpdates and filtering for VersionReadyEvent events.
As a result, the SwUpdate#availalbe observable is now redundant.

bazel

common

compiler

compiler-cli