PR Close #25582

PR Close #25582

PR Close #25582

PR Close #25618

PR Close #24206

PR Close #25984

PR Close #25370

Ivy depends on having the generic type token later when reading the ModuleWithProviders from a .d.ts file.

PR Close #25970

PR Close #25838

The version prefix issue has been fixed with
conventional-changelog/conventional-changelog#179.

PR Close #25838

PR Close #25917

This is a preliminary fix to make buildifier work with Bazel 0.16.

See alexeagle/angular-bazel-example/issues/173

PR Close #25917

The version was updated in https://github.com/angular/angular/commit/34ec9244a64787d3b8097b7d184d388fedc60118
but this file got missed.
PR Close #25992

Improve the grammar of the description to make it more readable.
PR Close #25901

The compiler should process all an entry-points dependencies
before processing that entry-point.

PR Close #25862

PR Close #25862

PR Close #25862

It turns out that `path.posix` does not always reliably
return forward slash paths on Windows.

PR Close #25862

PR Close #25920

PR Close #25988

PR Close #25969

`nodejs_binary` and `nodejs_test` from `@build_bazel_rules_nodejs//:defs.bzl` and `@build_bazel_rules_nodejs//internal/node:node.bzl` are different as the first one uses a macro https://github.com/bazelbuild/rules_nodejs/blob/master/internal/node/node.bzl#L229 to wrap the `nodejs_binary` and `nodejs_test` as an `.exe` for Windows.

PR Close #25940

this includes support for @ character in labels, which we need for fine-grained deps

PR Close #25967

Bazel version '0.16.1' doesn't seem to be available anymore! Upgrade to 0.17.1 instead.

PR Close #25967

Fixes #25938

PR Close #25939

PR Close #25958

PR Close #25933

PR Close #25931

PR Close #25895

fix(router): mount correct component if router outlet was not instantiated and if using a route reuse strategy (#25313) (#25314)

This unsets 'attachRef' on outlet context if no route is to be reused in route activation.

Closes #25313

PR Close #25314

PR Close #21840

Previously, when you attempted to bootstrap a component that had a
router-outlet using ngsummaries, it would complain that the component
was not provided by any module even if it was. This commit fixes a
mistake (AFAICT) which caused the lookup of the component in the AOT
summaries to fail.

I believe this change is safe. I've run the affected tests within Google
and there were no breakages caused by this change.

PR Close #24892

Fixes #25816

PR Close #25817

PR Close #25537

PR Close #25434

PR Close #25434

PR Close #25877

PR Close #25779

Create getter methods `getXXXDef` for each definition which
uses `hasOwnProperty` to verify that we don't accidently read form the
parent class.

Fixes: #24011
Fixes: #25026

PR Close #25736