angular / angular-cli

…HtmlWebpackPlugin

Webpack doesn't handle promise rejections properly. With this change use use a try/catch block and add the error to the compilation.

Closes #19893

…s options

A fallback value for stats options when an option is not defined. It has precedence over local webpack defaults.

while I was making myself familiar with the code-base
to solve an open issue, I saw this super minor typo
and decided to fix it

…known versions

This change adds logic to redirect module resolution requests for Angular schematics to ensure that the correct versions of core schematic related packages are used.  This also ensures that the runtime version of the schematics package matches the version used inside the schematic and that object instances passed into the schematic are compatible.
The current set of core schematic related packages are `@angular-devkit/*` and `@schematics/angular`.  Only first-party Angular schematics are currently affected by this change.

…kflow engine host

This adds an option to the NodeWorkflow to allow a custom NodeModulesEngineHost to be used with the workflow.

…ifferential loading enabled

Fixes #19849

Update to the latest version of bazel (4.0.0).

…test harness

…h the same filename

Previously when hashing of media was disabled, if 2 files had the same name. Only one files used to be emitted. With this change we change the behaviour so that both files are emitted.

Closes #12186

…ount for initial bundle size

Closes #17672

This fixes #11337 to allow for merging of a tree with another when the the file already exists in the tree being merged into.

This adds a spinner as well as shows more information regarding what package version was selected to be installed.

Closes #17983

TypeScript provides a set of pure functions for producing syntax tree nodes. Since TypeScript 4.0 these methods have been deprecated in favor of the factory API.

See: https://github.com/microsoft/TypeScript/wiki/API-Breaking-Changes#typescript-40

No need to update root `package.json` as it is already version `11.2.0-next.0`.

Update to the latest version of yarn.

…ne.js

This change causes native async functions to be downleveled when an application targets ES2017 within its TypeScript configuration.  Any source file that contains the async keyword will be processed including libraries.  Since Zone.js does not support native async, this processing allows Zone.js to function with an ES2017 target.

…ad from .npmrc

Before only first line end was being replaced.
Also, the replace value was incorrectly escaped.

The CA read from cafile being corrupt resulted in broken updates
when using registry with self-signed certificate.

The workaround till this is merged is to use `ca` or `ca[]` properties in `.npmrc`.

TypeScript provides a set of  pure  functions for producing syntax tree nodes. Since TypeScript 4.0 these methods have been deprecated in favor of the `factory` API.

See: https://github.com/microsoft/TypeScript/wiki/API-Breaking-Changes#typescript-40

…ipt methods

The flatten schema method has been deprecated without replacement.

Producing a flatten schema document does not in all cases produce a schema with identical behavior to the original.

See: https://json-schema.org/draft/2019-09/json-schema-core.html#rfc.appendix.B.2