…cription

Esbuild builder is stable and is no longer in developer preview.

(cherry picked from commit b9591eb)

An `ngHmrMode` boolean value will now be defined within application bundles.
The value is based on the development server's `hmr` option with `true`
when HMR is enabled and `false` when disabled. For all application builds,
the value will be `false`. `ngHmrMode` is similar in behavior to `ngServeMode`
or `ngDevMode`. It will not be present in the output code unless referenced
and in those cases only the final boolean value will be present if not optimized
out of the final code.
The value is not considered part of the public API and may change in the future.

(cherry picked from commit 318c164)

These command are outdated and no longer work

(cherry picked from commit 27fe5da)

Currently the `while` loop may either be causing the process to be
really stuck/hanging, or it somehow causes Node to exit.

This change makes the logic more robust and less CPU consuming.

(cherry picked from commit fe69a9b)

…ures

The karma configuration will now automatically set the `basePath` option
to the temporary output path when using the application build system's
karma testing. This ensures that only the relative path of the test files
is represented in the stack traces of test failures.

(cherry picked from commit f780e8b)

… with `@angular/platform-browser`

The Angular CLI expliclty adds `@angular/compiler` as a polyfill when JIT mode is enabled which makes using  `@angular/platform-browser-dynamic` redundant and causes the compiler to be imported twice.

(cherry picked from commit c0de723)

Compile time errors will now always be generated when an HTML template
and/or CSS component stylesheet are not present on disk. The Angular
compiler expects a return value of `null` from the `resourceNameToFileName`
function to indicate that a resource path does not exist. JIT mode previously
and continues to generate errors as expected.

(cherry picked from commit cb2ab43)