angular / components Public

Updates the linker integration test, which is an additional test we
run for the linker, besides running our tests with the linker.

The linker integration test ensures that the NPM package partial
compilation output can be processed properly, and ensures that there
are no unprocessable partial declarations.

Updates the peer dependency ranges for the v13 stable version:

* v13.0.0 of Angular Components requires at minimum a stable v13 version
  of Angular framework (no pre-releases allowed once we hit stable)

* For RxJS v7, minimum `7.4.0` is needed as that version comes with a
  ES2015 distibution wired up in the `package.json`, allowing for better
  optimized applications. This matches with `@angular/core` and the CLI.

angular/angular@48aa003//github.com/angular/angular/commit/48aa0039ea75693f751b26474029efdb6c223770

…ithub action (#23830)

Cleans up unused dependencies.

Updates to the latest version of the `dev-infra` package and fixes that we weren't enforcing formatting on `.mjs` files.

Updates the Firebase preview instance for the dev-app previews to an internal one with more capacity.

Removes the init test environment calls from the harness examples. This
is meant to make the examples a little more readable, and easier to
integrate within CLI projects (especially when are starting to use
a plain CLI project as foundation for our StackBlitz examples).

The CLI sets up the test environment in a global test init file, so
we should make this assumption in our examples as well. This also helps
with reducing duplication in our code base.

The `index.html` of the dev app assumes that the `DEV_APP_VARIABLES` global variable will always be present, but that's not the case when it is deployed. This causes an error which prevents the Google Maps script from loading.

These changes add a null check, as well as some docs about the `variables.json`.

…ework (#23873)

Updates all of our tooling to v13.0.0-rc.3 of the CLI/and framework.

Fixes a unit test that started failing, because it tries to scroll the page down, but there isn't enough content for it to scroll.

Automatically adds a class to the no data row so that it's easier to style.

In the process of adding the class I also noticed that the no data row doesn't have the correct `role`.

Fixes #23729.

* build: setup preview builds for dev-app

Sets up preview builds for the dev-app. Whenever the `dev-app preview`
label is applied to pull requests, a Github action will build the
dev-app using RBE and deploy it to a preview channel within a Firebase
project.

The deployment and building is split up into two individual workflows
to guarantee a secure exeuction of these steps. This follows the
concept as outlined in https://securitylab.github.com/research/github-actions-preventing-pwn-requests/.

In the future, we can try extracting some of this logic into a common
tool in the dev-infra repository.. allowing preview builds to be used
for other things, or in other repositories as well (or switching AIO
away from the rather-complicated docker preview build setup).

* fixup! build: setup preview builds for dev-app

Address feedback

* fixup! build: setup preview builds for dev-app

Update old links

Disables text selection inside `mat-icon` so that the text inside font icons can't be selected by accident.

* test: remove unnecessary boostrap module calls in size tests

* build: add comment explaining the processing of `.mjs` in esbuild rule

Adds a little comment explaining why`.mjs` is processed in the Angular
esbuild rule.

* build: update size test tool to work with Angular v13

Updates the size test tool to properly run with the Angular
v13 compilation pipeline, matching conceptually with what the
Angular CLI performs. i.e. running the Angular linker, running the
non-deprecated build-optimizer variant (i.e. the Babel plugins).

* test: update size-golden to reflect recent compilation pipeline changes

The new teardown behavior is enabled by default so we can drop the `teardown` flag usages.

…ortal code example (#23818)

Fixes that the husky pre-commit hook is not being executable,
causing it to be ignored by Husky.

Removes a past flat module bundle workaround that was needed when we
still shipped release packages with View Engine. The Angular compiler
picks the `index.ts` files as entry-point for the flat module bundles
(this whole flat module construct could be removed in the future anyway).

This was problematic because to avoid conflicts, the flat module out
file name was set to something unique that does not conflict with the
index file. The metadata JSON files for the `ng_module` targets (within our repo)
then did not reside next to the `index` files, but rather next to the
auto-generated flat module bundle. This broke the generation of
`defineInjectable` (which was used in VE as well) calls.

We worked around this in the past by patching the Angular compiler to
pick the public API file instead as entry-point; allowing us to let
the Angular compiler generate metadata and the bundle as `index.js` and
`index.metadata.json` (ensuring the release output worked then).

All of this is no longer needed with Ivy, so we can remove the
workaround and unblock angular/angular#43932
(which fails due to us patching some files in the compiler-cli package)

…when updating to v13 (#23752)

The Hammer gesture migration runs only for v9 and v10 but the global
post migration messages are printed regardless of whether the update
runs for v9 or v10. This commit fixes that by providing the target
version to the `globalPostMigration` functions for migrations.

Updates the default editor settings to format on save and to recommend the Prettier extension.

Fixes that the `approve-api` script was generating the wrong Bazel target for `google-maps` and `youtube-player`.

Fixes #23782.

This reverts commit ef7d9e0.

Bumps to the v14 Canary version of MDC.

Removes the `any` type used in the previous ts4.4 upgrade PR when
refering to the style property on the element. Creates a new type to
work around the built in `CSSStyleDeclaration` not including
`webkitTapHighlightColor`.

…due to pointerdown outside overlay (#23679)

Currently OverlayRef.outsidePointerEvents() emits when a user starts a click inside the overlay,
drags the cursor outside the overlay and releases the click (e.g. selecting text and moving the
mouse outside the overlay). In order to only emit when the click originates outside the overlay,
we track the target of the preceding pointerdown event and check if it originated from outside
the overlay.

Fixes #23643