Fix issue-related to the support of Safari TP versions. This issue was accidentally introduced in a0f9db8

Fixes #24639

(cherry picked from commit df7c7f4)

`querystring.stringify` will not remove undefined values.

(cherry picked from commit 7bcb19c)

…ipts instead of modules

This commit updates changes the way polyfills and runtime are loaded from modules to scripts. This is required as otherwise Jasmine will be loaded prior to Zone.js which causes clock patching not to work.

Closes #24651

(cherry picked from commit bf3be56)

…schematic

The bootstrapping wrapping is no longer necessary as of 15.1.3. See: angular/angular#48868

(cherry picked from commit 88fddc0)

… pattern does not match

Previously, we failed the compilation when the specified patterns did not match any spec file. This breaks the case were users configure Karma to not fail on empty test suit.

Closes #24644

(cherry picked from commit d9c697b)

When a schematic is executed, it is wrapped in a custom Node context. This context doesn't expose the same set of global variables. This can lead to an error if a schematic is importing the Angular compiler and the app is using i18n, because the `TextEncoder` isn't exposed through the custom context (see angular/angular#48940).

These changes add the `TextEncoder` to the context.

Fixes angular/angular#48940.

(cherry picked from commit 234f265)

…compliant downlevel class properties

The build optimizer's static class field pass will now additionally wrap
classes that contain side effect free class properties. This allows optimizers and
bundlers further along in the build pipeline to downlevel that class properties while
still retaining the ability to tree-shake the class if unused. The class properties
may need to be downleveled for a variety of reasons such as lack of browser support,
browser bugs with certain code structures, or to ensure spec-compliant runtime behavior.

(cherry picked from commit bfc0fac)