build: idiomatic install of @angular/bazel npm package (#26258)

* build: update ngcontainer to bazel 0.18.0

* build: update skylint to bazel 0.18

use .bazelignore file to ignore node_modules directory

.bazelignore

@@ -1,39 +1,2 @@
-# Bazel does not yet support wildcards or other .gitignore semantics for
-# .bazelignore. Two issues for this feature request are outstanding:
-# https://github.com/bazelbuild/bazel/issues/7093
-# https://github.com/bazelbuild/bazel/issues/8106
-.git
 node_modules
 dist
-
-# All integration test node_modules folders
-integration/animations/node_modules
-integration/cli-elements-universal/node_modules
-integration/cli-hello-world/node_modules
-integration/cli-hello-world-ivy-i18n/node_modules
-integration/cli-hello-world-lazy/node_modules
-integration/cli-hello-world-mocha/node_modules
-integration/cli-signal-inputs/node_modules
-integration/platform-server-hydration/node_modules
-integration/defer/node_modules
-integration/dynamic-compiler/node_modules
-integration/forms/node_modules
-integration/injectable-def/node_modules
-integration/ivy-i18n/node_modules
-integration/ng-add-localize/node_modules
-integration/ng_elements/node_modules
-integration/ng_update/node_modules
-integration/ng_update_migrations/node_modules
-integration/nodenext_resolution/node_modules
-integration/npm_package_archives.bzl/node_modules
-integration/platform-server/node_modules
-integration/service-worker-schema/node_modules
-integration/side-effects/node_modules
-integration/standalone-bootstrap/node_modules
-integration/terser/node_modules
-integration/trusted-types/node_modules
-integration/typings_test_rxjs7/node_modules
-integration/typings_test_ts49/node_modules
-integration/typings_test_ts50/node_modules
-integration/typings_test_ts51/node_modules
-integration/typings_test_ts52/node_modules

.bazelrc

@@ -1,71 +1,35 @@
-# Enable debugging tests with --config=debug
-test:debug --test_arg=--node_options=--inspect-brk --test_output=streamed --test_strategy=exclusive --test_timeout=9999 --nocache_test_results --spawn_strategy=local
+###############################
+# Typescript / Angular / Sass #
+###############################
 
-# Do not attempt to de-flake locally.
-# On CI we might set this to `3` to run with deflaking.
-test --flaky_test_attempts=1
+# Make compilation fast, by keeping a few copies of the compilers
+# running as daemons, and cache SourceFile AST's to reduce parse time.
+build --strategy=TypeScriptCompile=worker
+build --strategy=AngularTemplateCompile=worker
+
+# Enable debugging tests with --config=debug
+test:debug --test_arg=--node_options=--inspect-brk --test_output=streamed --test_strategy=exclusive --test_timeout=9999 --nocache_test_results
 
 ###############################
 # Filesystem interactions     #
 ###############################
 
-# Create symlinks in the project:
-# - dist/bin for outputs
-# - dist/testlogs, dist/genfiles
-# - bazel-out
-# NB: bazel-out should be excluded from the editor configuration.
-# The checked-in /.vscode/settings.json does this for VSCode.
-# Other editors may require manual config to ignore this directory.
-# In the past, we say a problem where VSCode traversed a massive tree, opening file handles and
+# Don't create symlinks like bazel-out in the project.
+# These cause VSCode to traverse a massive tree, opening file handles and
 # eventually a surprising failure with auto-discovery of the C++ toolchain in
 # MacOS High Sierra.
 # See https://github.com/bazelbuild/bazel/issues/4603
-build --symlink_prefix=dist/
+build --symlink_prefix=/
 
-# Turn off legacy external runfiles
-build --nolegacy_external_runfiles
-run --nolegacy_external_runfiles
-test --nolegacy_external_runfiles
-
-# Turn on --incompatible_strict_action_env which was on by default
-# in Bazel 0.21.0 but turned off again in 0.22.0. Follow
-# https://github.com/bazelbuild/bazel/issues/7026 for more details.
-# This flag is needed to so that the bazel cache is not invalidated
-# when running bazel via `yarn bazel`.
-# See https://github.com/angular/angular/issues/27514.
-build --incompatible_strict_action_env
-run --incompatible_strict_action_env
-test --incompatible_strict_action_env
-
-# Do not build runfile trees by default. If an execution strategy relies on runfile
-# symlink teee, the tree is created on-demand. See: https://github.com/bazelbuild/bazel/issues/6627
-# and https://github.com/bazelbuild/bazel/commit/03246077f948f2790a83520e7dccc2625650e6df
-build --nobuild_runfile_links
-
-build --enable_runfiles
+# Performance: avoid stat'ing input files
+build --watchfs
 
 ###############################
 # Release support             #
-# Turn on these settings with #
-#  --config=release           #
 ###############################
 
 # Releases should always be stamped with version control info
-# This command assumes node on the path and is a workaround for
-# https://github.com/bazelbuild/bazel/issues/4802
-build:release --workspace_status_command="yarn -s ng-dev release build-env-stamp --mode=release"
-build:release --stamp
-
-# Snapshots should also be stamped with version control information.
-build:snapshot-build --workspace_status_command="yarn -s ng-dev release build-env-stamp --mode=snapshot"
-build:snapshot-build --stamp
-
-# Angular DevTools for Firefox releases *cannot* be stamped and `--config snapshot-build-firefox` is a no-op.
-# This is because Mozilla requires add-on source code to be uploaded and then they manually reproduce the build.
-# If we stamp the build based on Git information such as the current commit, then reproducing the build would require
-# uploading the entire `.git` directory. We already must upload the entire monorepo, and uploading `.git` as well
-# exceeds the max source file size. To address this, we just *don't* stamp Firefox builds of Angular DevTools.
-build:snapshot-build-firefox --nostamp
+build --workspace_status_command=./tools/bazel_stamp_vars.sh
 
 ###############################
 # Output                      #
@@ -78,93 +42,21 @@ query --output=label_kind
 # By default, failing tests don't print any output, it goes to the log file
 test --test_output=errors
 
-##################################
-# Remote Build Execution support #
-# Turn on these settings with    #
-#  --config=remote               #
-##################################
+# Show which actions are run under workers,
+# and print all the actions running in parallel.
+# Helps to demonstrate that bazel uses all the cores on the machine.
+build --experimental_ui
+test --experimental_ui
 
-# The following --define=EXECUTOR=remote will be able to be removed
-# once https://github.com/bazelbuild/bazel/issues/7254 is fixed
-build:remote --define=EXECUTOR=remote
+################################
+# Settings for CircleCI        #
+################################
 
-# Set a higher timeout value, just in case.
-build:remote --remote_timeout=600
+# Bazel flags for CircleCI are in /.circleci/bazel.rc
 
-# Bazel detects maximum number of jobs based on host resources.
-# Since we run remotely, we can increase this number significantly.
-common:remote --jobs=200
-
-build:remote --google_default_credentials
-
-# Force remote exeuctions to consider the entire run as linux
-build:remote --cpu=k8
-build:remote --host_cpu=k8
-
-# Toolchain and platform related flags
-build:remote --extra_execution_platforms=@npm//@angular/build-tooling/bazel/remote-execution:platform
-build:remote --host_platform=@npm//@angular/build-tooling/bazel/remote-execution:platform
-build:remote --platforms=@npm//@angular/build-tooling/bazel/remote-execution:platform
-
-# Remote instance and caching
-build:remote --remote_instance_name=projects/internal-200822/instances/primary_instance
-build:remote --bes_instance_name=internal-200822
-build:remote --remote_cache=remotebuildexecution.googleapis.com
-build:remote --remote_executor=remotebuildexecution.googleapis.com
-build:remote --remote_upload_local_results=false
-
-# See: https://docs.google.com/document/d/1NgDPsCIwprDdqC1zj0qQrh5KGK2hQTSTux1DAvi4rSc/edit?tab=t.0.
-build:remote --experimental_remote_execution_keepalive
-
-# Use HTTP remote cache
-build:remote-cache --remote_cache=https://storage.googleapis.com/angular-team-cache
-build:remote-cache --remote_accept_cached=true
-build:remote-cache --remote_upload_local_results=false
-build:remote-cache --google_default_credentials
-
-# Additional flags added when running a "trusted build" with additional access
-build:trusted-build --remote_upload_local_results=true
-
-# Ensure that tags like "no-remote-exec" get propagated to actions created by rules,
-# even if the rule implementation does not explicitly pass them to the execution requirements.
-# https://bazel.build/reference/command-line-reference#flag--experimental_allow_tags_propagation
-common --experimental_allow_tags_propagation
-
-# Disable network access in the sandbox by default. To enable network access
-# for a particular target, use:
-#
-# load("@npm//@angular/build-tooling/bazel/remote-execution:index.bzl", "ENABLE_NETWORK")
-# my_target(
-#   ...,
-#   exec_properties = ENABLE_NETWORK,   # Enables network in remote exec
-#   tags = ["requires-network"]         # Enables network in sandbox
-# )
-build --nosandbox_default_allow_network
-
-##################################
-# Saucelabs tests settings       #
-# Turn on these settings with    #
-#  --config=saucelabs            #
-##################################
-
-# For saucelabs tests we don't want to enable flaky test attempts. Karma has its own integrated
-# retry mechanism and we do not want to retry unnecessarily if Karma already tried multiple times.
-test:saucelabs --flaky_test_attempts=1
-
-################
-# Flag Aliases #
-################
-
-# --ng_perf will ask the Ivy compiler to produce performance results for each build.
-build --flag_alias=ng_perf=//packages/compiler-cli:ng_perf
-# --prerender_adev will run adev build/serve in a full mode, performing prerendering
-build --flag_alias=prerender_adev=//adev:prerender_adev
-
-####################################################
-# User bazel configuration
-# NOTE: This needs to be the *last* entry in the config.
-####################################################
-
-# Load any settings which are specific to the current user. Needs to be *last* statement
-# in this config, as the user configuration should be able to overwrite flags from this file.
-try-import %workspace%/.bazelrc.user
+################################
+# Temporary Settings for Ivy   #
+################################
+# to determine if the compiler used should be Ivy or ViewEngine one can use `--define=compile=local` on
+# any bazel target. This is a temporary flag until codebase is permanently switched to Ivy.
+build --define=compile=legacy

.bazelversion

@@ -1 +0,0 @@
-5.0.0

.bowerrc

@@ -0,0 +1,3 @@
+{
+  "directory" : "bower_components"
+}

.circleci/README.md

@@ -12,8 +12,8 @@ We use this as a symmetric AES encryption key to encrypt tokens like
 a GitHub token that enables publishing snapshots.
 
 To create the github_token file, we take this approach:
-- Find the angular-builds:token in the internal pw database
-- Go inside the CircleCI default docker image so you use the same version of openssl as we will at runtime: `docker run --rm -it circleci/node:10.12`
+- Find the angular-builds:token in http://valentine
+- Go inside the ngcontainer docker image so you use the same version of openssl as we will at runtime: `docker run --rm -it angular/ngcontainer`
 - echo "https://[token]:@github.com" > credentials
 - openssl aes-256-cbc -e -in credentials -out .circleci/github_token -k $KEY
-- If needed, base64-encode the result so you can copy-paste it out of docker: `base64 github_token`
+- If needed, base64-encode the result so you can copy-paste it out of docker: `base64 github_token`

.circleci/bazel.common.rc

@@ -1,16 +0,0 @@
-# Settings in this file should be OS agnostic. Use the bazel.<OS>.rc files for OS specific settings.
-
-# Print all the options that apply to the build.
-# This helps us diagnose which options override others
-# (e.g. /etc/bazel.bazelrc vs. tools/bazel.rc)
-build --announce_rc
-
-# Retry in the event of flakes, eg. https://circleci.com/gh/angular/angular/31309
-# By default this is set in the project `.bazelrc` to `1`.
-test --flaky_test_attempts=3
-
-# More details on failures
-build --verbose_failures=true
-
-# CI supports colors but Bazel does not detect it.
-common --color=yes

.circleci/bazel.linux.rc

@@ -1,23 +0,0 @@
-# These options are enabled when running on CI
-# We do this by copying this file to /etc/bazel.bazelrc at the start of the build.
-# See documentation in /docs/BAZEL.md
-
-# Import config items common to both Linux and Windows setups.
-# https://docs.bazel.build/versions/master/guide.html#bazelrc-syntax-and-semantics
-try-import %workspace%/.circleci/bazel.common.rc
-
-# Save downloaded repositories in a location that can be cached by CircleCI. This helps us
-# speeding up the analysis time significantly with Bazel managed node dependencies on the CI.
-build --repository_cache=/home/circleci/bazel_repository_cache
-
-# Workaround https://github.com/bazelbuild/bazel/issues/3645
-# Bazel doesn't calculate the memory ceiling correctly when running under Docker.
-# Limit Bazel to consuming resources that fit in CircleCI "2xlarge+" class
-# https://circleci.com/docs/2.0/configuration-reference/#resource_class
-build --local_cpu_resources=20
-build --local_ram_resources=40960
-
-# All build executed remotely should be done using our RBE configuration.
-build:remote --google_default_credentials
-
-build --config=remote

.circleci/bazel.rc

@@ -0,0 +1,33 @@
+# These options are enabled when running on CI
+# We do this by copying this file to /etc/bazel.bazelrc at the start of the build.
+# See remote cache documentation in /docs/BAZEL.md
+
+# Don't be spammy in the logs
+# TODO(gmagolan): Hide progress again once build performance improves
+# Presently, CircleCI can timeout during bazel test ... with the following
+# error: Too long with no output (exceeded 10m0s)
+# build --noshow_progress
+
+# Don't run manual tests
+test --test_tag_filters=-manual
+
+# Print all the options that apply to the build.
+# This helps us diagnose which options override others
+# (e.g. /etc/bazel.bazelrc vs. tools/bazel.rc)
+build --announce_rc
+
+# Create dist/bin symlink to $(bazel info bazel-bin)
+# We use this when uploading artifacts after the build finishes
+build --symlink_prefix=dist/
+
+# Workaround https://github.com/bazelbuild/bazel/issues/3645
+# Bazel doesn't calculate the memory ceiling correctly when running under Docker.
+# Limit Bazel to consuming resources that fit in CircleCI "xlarge" class
+# https://circleci.com/docs/2.0/configuration-reference/#resource_class
+build --local_resources=14336,8.0,1.0
+
+# Retry in the event of flakes, eg. https://circleci.com/gh/angular/angular/31309
+test --flaky_test_attempts=2
+
+# More details on failures
+build --verbose_failures=true

.circleci/bazel.windows.rc

@@ -1,17 +0,0 @@
-# These options are enabled when running on CI
-# We do this by copying this file to $env:ProgramData\bazel.bazelrc at the start of the build.
-# See documentation in /docs/BAZEL.md
-
-# Import config items common to both Linux and Windows setups.
-# https://docs.bazel.build/versions/master/guide.html#bazelrc-syntax-and-semantics
-try-import %workspace%/.circleci/bazel.common.rc
-
-# Manually set the local resources used in windows CI runs
-build --local_ram_resources=120000
-build --local_cpu_resources=32
-
-# All windows jobs run on master and should use http caching
-build --remote_http_cache=https://storage.googleapis.com/angular-team-cache
-build --remote_accept_cached=true
-build --remote_upload_local_results=true
-build --google_default_credentials

.circleci/config.yml

@@ -1,16 +1,310 @@
-# This config is remaining in place to prevent pull requests failing because of CircleCI config missing.
+# Configuration file for https://circleci.com/gh/angular/angular
 
-version: 2.1
+# Note: YAML anchors allow an object to be re-used, reducing duplication.
+# The ampersand declares an alias for an object, then later the `<<: *name`
+# syntax dereferences it.
+# See http://blog.daemonl.com/2016/02/yaml.html
+# To validate changes, use an online parser, eg.
+# http://yaml-online-parser.appspot.com/
 
+# Variables
+
+## IMPORTANT
+# If you change the `docker_image` version, also change the `cache_key` suffix and the version of
+# `com_github_bazelbuild_buildtools` in the `/WORKSPACE` file.
+var_1: &docker_image angular/ngcontainer:0.7.0
+var_2: &cache_key v2-angular-{{ .Branch }}-{{ checksum "yarn.lock" }}-0.7.0
+
+# Define common ENV vars
+var_3: &define_env_vars
+  run: echo "export PROJECT_ROOT=$(pwd)" >> $BASH_ENV
+
+# See remote cache documentation in /docs/BAZEL.md
+var_4: &setup-bazel-remote-cache
+  run:
+    name: Start up bazel remote cache proxy
+    command: ~/bazel-remote-proxy -backend circleci://
+    background: true
+
+var_5: &setup_bazel_remote_execution
+  run:
+    name: "Setup bazel RBE remote execution"
+    command: openssl aes-256-cbc -d -in .circleci/gcp_token -k "${CIRCLE_PROJECT_REPONAME}" -out /home/circleci/.gcp_credentials && echo "export GOOGLE_APPLICATION_CREDENTIALS=/home/circleci/.gcp_credentials" >> $BASH_ENV && sudo bash -c "cat .circleci/rbe-bazel.rc >> /etc/bazel.bazelrc"
+
+# Settings common to each job
+anchor_1: &job_defaults
+  working_directory: ~/ng
+  docker:
+    - image: *docker_image
+
+# After checkout, rebase on top of master.
+# Similar to travis behavior, but not quite the same.
+# See https://discuss.circleci.com/t/1662
+anchor_2: &post_checkout
+  post: git pull --ff-only origin "refs/pull/${CIRCLE_PULL_REQUEST//*pull\//}/merge"
+
+version: 2
 jobs:
-  pass:
-    docker:
-      - image: cimg/base:2022.05
+  lint:
+    <<: *job_defaults
+    resource_class: xlarge
     steps:
-      - run: echo "This too shall pass (always)"
+      - checkout:
+          <<: *post_checkout
+      - run: sudo cp .circleci/bazel.rc /etc/bazel.bazelrc
+
+      # Check BUILD.bazel formatting before we have a node_modules directory
+      # Then we don't need any exclude pattern to avoid checking those files
+      - run: 'yarn buildifier -mode=check ||
+              (echo "BUILD files not formatted. Please run ''yarn buildifier''" ; exit 1)'
+      # Run the skylark linter to check our Bazel rules
+      - run: 'yarn skylint ||
+              (echo -e "\n.bzl files have lint errors. Please run ''yarn skylint''"; exit 1)'
+
+      - restore_cache:
+          key: *cache_key
+
+      - run: yarn install --frozen-lockfile --non-interactive
+      - run: ./node_modules/.bin/gulp lint
+
+  test:
+    <<: *job_defaults
+    resource_class: xlarge
+    steps:
+      - *define_env_vars
+      - checkout:
+          <<: *post_checkout
+      - run: sudo cp .circleci/bazel.rc /etc/bazel.bazelrc
+
+      - run: bazel info release
+      - run: bazel run @nodejs//:yarn
+      # Use bazel query so that we explicitly ask for all buildable targets to be built as well
+      # This avoids waiting for the slowest build target to finish before running the first test
+      # See https://github.com/bazelbuild/bazel/issues/4257
+      # NOTE: Angular developers should typically just bazel build //packages/... or bazel test //packages/...
+      # Setup remote execution and run RBE-compatible tests.
+      - *setup_bazel_remote_execution
+      - run: bazel query --output=label //... | xargs bazel test --build_tag_filters=-ivy-only --test_tag_filters=-manual,-ivy-only,-local
+      # Now run RBE incompatible tests locally.
+      - run: sudo cp .circleci/bazel.rc /etc/bazel.bazelrc
+      - run: bazel query --output=label //... | xargs bazel test --build_tag_filters=-ivy-only,local --test_tag_filters=-manual,-ivy-only,local
+
+      # CircleCI will allow us to go back and view/download these artifacts from past builds.
+      # Also we can use a service like https://buildsize.org/ to automatically track binary size of these artifacts.
+      # The destination keys need be format {projectName}/{context}/{fileName} so that the github-robot can process them for size calculations
+      # projectName should remain consistant to group files
+      # context and fileName can be almost anything (within usual URI rules)
+      # There should only be exactly 2 forward slashes in the path
+      # This is so they're backwards compatiable with the existing data we have on bundle sizes
+      - store_artifacts:
+          path: dist/bin/packages/core/test/bundling/hello_world/bundle.min.js
+          destination: core/hello_world/bundle
+      - store_artifacts:
+          path: dist/bin/packages/core/test/bundling/todo/bundle.min.js
+          destination: core/todo/bundle
+      - store_artifacts:
+          path: dist/bin/packages/core/test/bundling/hello_world/bundle.min.js.br
+          destination: core/hello_world/bundle.br
+      - store_artifacts:
+          path: dist/bin/packages/core/test/bundling/todo/bundle.min.js.br
+          destination: core/todo/bundle.br
+      - save_cache:
+          key: *cache_key
+          paths:
+            - "node_modules"
+            - "~/bazel_repository_cache"
+
+  # Temporary job to test what will happen when we flip the Ivy flag to true
+  test_ivy_jit:
+    <<: *job_defaults
+    resource_class: xlarge
+    steps:
+      - *define_env_vars
+      - checkout:
+          <<: *post_checkout
+      - run: sudo cp .circleci/bazel.rc /etc/bazel.bazelrc
+
+      - run: bazel run @yarn//:yarn
+      - *setup_bazel_remote_execution
+      - run: bazel query --output=label //... | xargs bazel test --define=compile=jit --build_tag_filters=ivy-jit --test_tag_filters=-manual,ivy-jit
+
+  test_ivy_aot:
+    <<: *job_defaults
+    resource_class: xlarge
+    steps:
+      - *define_env_vars
+      - checkout:
+          <<: *post_checkout
+      - run: sudo cp .circleci/bazel.rc /etc/bazel.bazelrc
+
+      - run: bazel run @yarn//:yarn
+      - *setup_bazel_remote_execution
+      - run: bazel query --output=label //... | xargs bazel test --define=compile=local --build_tag_filters=ivy-local --test_tag_filters=-manual,ivy-local
+
+  # This job should only be run on PR builds, where `CIRCLE_PR_NUMBER` is defined.
+  aio_preview:
+    <<: *job_defaults
+    environment:
+       AIO_SNAPSHOT_ARTIFACT_PATH: &aio_preview_artifact_path 'aio/tmp/snapshot.tgz'
+    steps:
+      - checkout:
+          <<: *post_checkout
+      - restore_cache:
+          key: *cache_key
+      - run: yarn install --frozen-lockfile --non-interactive
+      - run: ./aio/scripts/build-artifacts.sh $AIO_SNAPSHOT_ARTIFACT_PATH $CIRCLE_PR_NUMBER $CIRCLE_SHA1
+      - store_artifacts:
+          path: *aio_preview_artifact_path
+          # The `destination` needs to be kept in synch with the value of
+          # `AIO_ARTIFACT_PATH` in `aio/aio-builds-setup/Dockerfile`
+          destination: aio/dist/aio-snapshot.tgz
+
+  # This job should only be run on PR builds, where `CIRCLE_PR_NUMBER` is defined.
+  test_aio_preview:
+    <<: *job_defaults
+    steps:
+      - checkout:
+          <<: *post_checkout
+      - restore_cache:
+          key: *cache_key
+      - run: yarn install --cwd aio --frozen-lockfile --non-interactive
+      - run:
+          name: Wait for preview and run tests
+          command: |
+            source "./scripts/ci/env.sh" print
+            xvfb-run --auto-servernum node aio/scripts/test-preview.js $CIRCLE_PR_NUMBER $CIRCLE_SHA1 $AIO_MIN_PWA_SCORE
+
+  # This job exists only for backwards-compatibility with old scripts and tests
+  # that rely on the pre-Bazel dist/packages-dist layout.
+  # It duplicates some work with the job above: we build the bazel packages
+  # twice. Even though we have a remote cache, these jobs will typically run in
+  # parallel so up-to-date outputs will not be available at the time the build
+  # starts.
+  # No new jobs should depend on this one.
+  build-packages-dist:
+    <<: *job_defaults
+    resource_class: xlarge
+    steps:
+      - *define_env_vars
+      - checkout:
+          <<: *post_checkout
+      - run: sudo cp .circleci/bazel.rc /etc/bazel.bazelrc
+      - run: bazel run @nodejs//:yarn
+      - *setup_bazel_remote_execution
+      - run: scripts/build-packages-dist.sh
+
+      # Save the npm packages from //packages/... for other workflow jobs to read
+      # https://circleci.com/docs/2.0/workflows/#using-workspaces-to-share-data-among-jobs
+      - persist_to_workspace:
+          root: dist
+          paths:
+            - packages-dist
+            - packages-dist-ivy-jit
+            - packages-dist-ivy-local
+
+  # We run the integration tests outside of Bazel for now.
+  # They are a separate workflow job so that they can be easily re-run.
+  # When the tests are ported to bazel test targets, they should move to the "test"
+  # job above, as part of the bazel test command. That has flaky_test_attempts so the
+  # need to re-run manually should be alleviated.
+  # See comments inside the integration/run_tests.sh script.
+  integration_test:
+    <<: *job_defaults
+    # Note: we run Bazel in one of the integration tests, and it can consume >2G
+    # of memory. Together with the system under test, this can exhaust the RAM
+    # on a 4G worker so we use a larger machine here too.
+    resource_class: xlarge
+    steps:
+      - *define_env_vars
+      - checkout:
+          <<: *post_checkout
+      - attach_workspace:
+          at: dist
+      - run: xvfb-run --auto-servernum ./integration/run_tests.sh
+
+  # This job updates the content of repos like github.com/angular/core-builds
+  # for every green build on angular/angular.
+  publish_snapshot:
+    <<: *job_defaults
+    steps:
+      # See below - ideally this job should not trigger for non-upstream builds.
+      # But since it does, we have to check this condition.
+      - run:
+          name: Skip this job for Pull Requests and Fork builds
+          # Note, `|| true` on the end makes this step always exit 0
+          command: '[[
+              -v CIRCLE_PR_NUMBER
+              || "$CIRCLE_PROJECT_USERNAME" != "angular"
+              || "$CIRCLE_PROJECT_REPONAME" != "angular"
+          ]] && circleci step halt || true'
+      - checkout:
+          <<: *post_checkout
+      - attach_workspace:
+          at: dist
+      # CircleCI has a config setting to force SSH for all github connections
+      # This is not compatible with our mechanism of using a Personal Access Token
+      # Clear the global setting
+      - run: git config --global --unset "url.ssh://git@github.com.insteadof"
+      - run:
+          name: Decrypt github credentials
+          command: 'openssl aes-256-cbc -d -in .circleci/github_token -k "${KEY}" -out ~/.git_credentials'
+      - run: ./scripts/ci/publish-build-artifacts.sh
+
+  aio_monitoring:
+    <<: *job_defaults
+    steps:
+      - checkout:
+          <<: *post_checkout
+      - restore_cache:
+          key: *cache_key
+      - run: xvfb-run --auto-servernum ./aio/scripts/test-production.sh
 
 workflows:
   version: 2
   default_workflow:
     jobs:
-      - pass
+      - lint
+      - test
+      - test_ivy_jit
+      - test_ivy_aot
+      - build-packages-dist
+      - aio_preview:
+          # Only run on PR builds. (There can be no previews for non-PR builds.)
+          filters:
+            branches:
+              only: /pull\/\d+/
+      - test_aio_preview:
+          requires:
+            - aio_preview
+      - integration_test:
+          requires:
+            - build-packages-dist
+      - publish_snapshot:
+          # Note: no filters on this job because we want it to run for all upstream branches
+          # We'd really like to filter out pull requests here, but not yet available:
+          # https://discuss.circleci.com/t/workflows-pull-request-filter/14396/4
+          # Instead, the job just exits immediately at the first step.
+          requires:
+            # Only publish if tests and integration tests pass
+            - test
+            - test_ivy_jit
+            - test_ivy_aot
+            - integration_test
+            # Get the artifacts to publish from the build-packages-dist job
+            # since the publishing script expects the legacy outputs layout.
+            - build-packages-dist
+
+  aio_monitoring:
+    jobs:
+      - aio_monitoring
+    triggers:
+      - schedule:
+          cron: "0 0 * * *"
+          filters:
+            branches:
+              only:
+                - master
+
+notify:
+  webhooks:
+    - url: https://ngbuilds.io/circle-build

.circleci/env-helpers.inc.sh

@@ -1,76 +0,0 @@
-####################################################################################################
-# Helpers for defining environment variables for CircleCI.
-#
-# In CircleCI, each step runs in a new shell. The way to share ENV variables across steps is to
-# export them from `$BASH_ENV`, which is automatically sourced at the beginning of every step (for
-# the default `bash` shell).
-#
-# See also https://circleci.com/docs/2.0/env-vars/#using-bash_env-to-set-environment-variables.
-####################################################################################################
-
-# Set and print an environment variable.
-#
-# Use this function for setting environment variables that are public, i.e. it is OK for them to be
-# visible to anyone through the CI logs.
-#
-# Usage: `setPublicVar <name> <value>`
-function setPublicVar() {
-  setSecretVar $1 "$2";
-  echo "$1=$2";
-}
-
-# Set (without printing) an environment variable.
-#
-# Use this function for setting environment variables that are secret, i.e. should not be visible to
-# everyone through the CI logs.
-#
-# Usage: `setSecretVar <name> <value>`
-function setSecretVar() {
-  # WARNING: Secrets (e.g. passwords, access tokens) should NOT be printed.
-  # (Keep original shell options to restore at the end.)
-  local -r originalShellOptions=$(set +o);
-  set +x -eu -o pipefail;
-
-  local assignmentStatement="export $1=\"${2:-}\";"
-
-  echo "${assignmentStatement}" >> $BASH_ENV;
-  eval "${assignmentStatement}"
-
-  # Restore original shell options.
-  eval "$originalShellOptions";
-}
-
-
-# Create a function to set an environment variable, when called.
-#
-# Use this function for creating setter for public environment variables that require expensive or
-# time-consuming computations and may not be needed. When needed, you can call this function to set
-# the environment variable (which will be available through `$BASH_ENV` from that point onwards).
-#
-# Arguments:
-# - `<name>`: The name of the environment variable. The generated setter function will be
-#   `setPublicVar_<name>`.
-# - `<code>`: The code to run to compute the value for the variable. Since this code should be
-#   executed lazily, it must be properly escaped. For example:
-#   ```sh
-#   # DO NOT do this:
-#   createPublicVarSetter MY_VAR "$(whoami)";  # `whoami` will be evaluated eagerly
-#
-#   # DO this isntead:
-#   createPublicVarSetter MY_VAR "\$(whoami)";  # `whoami` will NOT be evaluated eagerly
-#   ```
-#
-# Usage: `createPublicVarSetter <name> <code>`
-#
-# Example:
-# ```sh
-# createPublicVarSetter MY_VAR 'echo "FOO"';
-# echo $MY_VAR;  # Not defined
-#
-# setPublicVar_MY_VAR;
-# source $BASH_ENV;
-# echo $MY_VAR;  # FOO
-# ```
-function createPublicVarSetter() {
-  echo "setPublicVar_$1() { setPublicVar $1 \"$2\"; }" >> $BASH_ENV;
-}

.circleci/env.linux.sh

@@ -1,4 +0,0 @@
-####################################################################################################
-# Set bazel configuration for CircleCI runs.
-####################################################################################################
-cp "${PROJECT_ROOT}/.circleci/bazel.linux.rc" ".bazelrc.user";

.circleci/env.sh

@@ -1,88 +0,0 @@
-#!/usr/bin/env bash
-
-# Variables
-readonly projectDir=$(realpath "$(dirname ${BASH_SOURCE[0]})/..")
-readonly envHelpersPath="$projectDir/.circleci/env-helpers.inc.sh";
-
-# Load helpers and make them available everywhere (through `$BASH_ENV`).
-source $envHelpersPath;
-echo "source $envHelpersPath;" >> $BASH_ENV;
-
-
-####################################################################################################
-# Define PUBLIC environment variables for CircleCI.
-####################################################################################################
-# See https://circleci.com/docs/2.0/env-vars/#built-in-environment-variables for more info.
-####################################################################################################
-setPublicVar CI "$CI"
-setPublicVar PROJECT_ROOT "$projectDir";
-# This is the branch being built; e.g. `pull/12345` for PR builds.
-setPublicVar CI_BRANCH "$CIRCLE_BRANCH";
-setPublicVar CI_BUILD_URL "$CIRCLE_BUILD_URL";
-setPublicVar CI_COMMIT "$CIRCLE_SHA1";
-# `CI_COMMIT_RANGE` is only used on push builds (a.k.a. non-PR, non-scheduled builds and rerun
-# workflows of such builds).
-setPublicVar CI_GIT_BASE_REVISION "${CIRCLE_GIT_BASE_REVISION}";
-setPublicVar CI_GIT_REVISION "${CIRCLE_GIT_REVISION}";
-setPublicVar CI_COMMIT_RANGE "$CIRCLE_GIT_BASE_REVISION..$CIRCLE_GIT_REVISION";
-setPublicVar CI_PULL_REQUEST "${CIRCLE_PR_NUMBER:-false}";
-setPublicVar CI_REPO_NAME "$CIRCLE_PROJECT_REPONAME";
-setPublicVar CI_REPO_OWNER "$CIRCLE_PROJECT_USERNAME";
-setPublicVar CI_PR_REPONAME "$CIRCLE_PR_REPONAME";
-setPublicVar CI_PR_USERNAME "$CIRCLE_PR_USERNAME";
-
-
-####################################################################################################
-# Define "lazy" PUBLIC environment variables for CircleCI.
-# (I.e. functions to set an environment variable when called.)
-####################################################################################################
-createPublicVarSetter CI_STABLE_BRANCH "\$(npm info @angular/core dist-tags.latest | sed -r 's/^\\s*([0-9]+\\.[0-9]+)\\.[0-9]+.*$/\\1.x/')";
-
-
-####################################################################################################
-# Define SECRET environment variables for CircleCI.
-####################################################################################################
-setSecretVar CI_SECRET_AIO_DEPLOY_FIREBASE_TOKEN "$AIO_DEPLOY_TOKEN";
-setSecretVar CI_SECRET_PAYLOAD_FIREBASE_TOKEN "$ANGULAR_PAYLOAD_TOKEN";
-
-
-####################################################################################################
-# Define SauceLabs environment variables for CircleCI.
-####################################################################################################
-setPublicVar SAUCE_USERNAME "angular-framework";
-setSecretVar SAUCE_ACCESS_KEY "f4bf7c639c5a-c6bb-d6a4-a4b5-800aa111";
-# TODO(josephperrott): Remove environment variables once all saucelabs tests are via bazel method.
-setPublicVar SAUCE_LOG_FILE /tmp/angular/sauce-connect.log
-setPublicVar SAUCE_READY_FILE /tmp/angular/sauce-connect-ready-file.lock
-setPublicVar SAUCE_PID_FILE /tmp/angular/sauce-connect-pid-file.lock
-setPublicVar SAUCE_TUNNEL_IDENTIFIER "angular-framework-${CIRCLE_BUILD_NUM}-${CIRCLE_NODE_INDEX}"
-# Amount of seconds we wait for sauceconnect to establish a tunnel instance. In order to not
-# acquire CircleCI instances for too long if sauceconnect failed, we need a connect timeout.
-setPublicVar SAUCE_READY_FILE_TIMEOUT 120
-
-####################################################################################################
-# Create shell script in /tmp for Bazel actions to access CI envs without
-# busting the cache. Used by payload-size.sh script in integration tests.
-####################################################################################################
-readonly bazelVarEnv="/tmp/bazel-ci-env.sh"
-echo "# Setup by /.circle/env.sh" > $bazelVarEnv
-echo "export PROJECT_ROOT=\"${PROJECT_ROOT}\";" >> $bazelVarEnv
-echo "export CI_BRANCH=\"${CI_BRANCH}\";" >> $bazelVarEnv
-echo "export CI_BUILD_URL=\"${CI_BUILD_URL}\";" >> $bazelVarEnv
-echo "export CI_COMMIT=\"${CI_COMMIT}\";" >> $bazelVarEnv
-echo "export CI_PULL_REQUEST=\"${CI_PULL_REQUEST}\";" >> $bazelVarEnv
-echo "export CI_REPO_NAME=\"${CI_REPO_NAME}\";" >> $bazelVarEnv
-echo "export CI_REPO_OWNER=\"${CI_REPO_OWNER}\";" >> $bazelVarEnv
-echo "export CI_SECRET_PAYLOAD_FIREBASE_TOKEN=\"${CI_SECRET_PAYLOAD_FIREBASE_TOKEN}\";" >> $bazelVarEnv
-
-####################################################################################################
-# Platform-specific environment setup (which can leverage the base variables from here)
-####################################################################################################
-
-# Conditionally, load additional environment settings based on the current VM
-# operating system running. We detect Windows by checking for `%AppData%`.
-if [[ -n "${APPDATA}" ]]; then
-  source ${projectDir}/.circleci/env.windows.sh
-else
-  source ${projectDir}/.circleci/env.linux.sh
-fi

.circleci/env.windows.sh

@@ -1,13 +0,0 @@
-####################################################################################################
-# Set bazel configuration for CircleCI runs.
-####################################################################################################
-cp "${PROJECT_ROOT}/.circleci/bazel.windows.rc" ".bazelrc.user";
-
-# Override the `PATH` environment variable so that the windows-nvm NodeJS version
-# always has precedence over potential existing NodeJS versions from the image.
-setPublicVar PATH "/c/Program Files/nodejs/:$PATH"
-
-# Expose the Bazelisk version. We need to run Bazelisk globally since Windows has problems launching
-# Bazel from a node modules directoy that might be modified by the Bazel Yarn install then.
-setPublicVar BAZELISK_VERSION \
-    "$(cd ${PROJECT_ROOT}; node -p 'require("./package.json").devDependencies["@bazel/bazelisk"]')"

.circleci/rbe-bazel.rc

@@ -0,0 +1,77 @@
+# These options are enabled when running on CI with Remote Build Execution.
+
+################################################################
+# Toolchain related flags for remote build execution.          #
+################################################################
+# Remote Build Execution requires a strong hash function, such as SHA256.
+startup --host_jvm_args=-Dbazel.DigestFunction=SHA256
+
+# Depending on how many machines are in the remote execution instance, setting
+# this higher can make builds faster by allowing more jobs to run in parallel.
+# Setting it too high can result in jobs that timeout, however, while waiting
+# for a remote machine to execute them.
+build --jobs=150
+
+# Set several flags related to specifying the platform, toolchain and java
+# properties.
+# These flags are duplicated rather than imported from (for example)
+# %workspace%/configs/ubuntu16_04_clang/1.0/toolchain.bazelrc to make this
+# bazelrc a standalone file that can be copied more easily.
+# These flags should only be used as is for the rbe-ubuntu16-04 container
+# and need to be adapted to work with other toolchain containers.
+build --host_javabase=@bazel_toolchains//configs/ubuntu16_04_clang/1.0:jdk8
+build --javabase=@bazel_toolchains//configs/ubuntu16_04_clang/1.0:jdk8
+build --host_java_toolchain=@bazel_tools//tools/jdk:toolchain_hostjdk8
+build --java_toolchain=@bazel_tools//tools/jdk:toolchain_hostjdk8
+build --crosstool_top=@bazel_toolchains//configs/ubuntu16_04_clang/1.0/bazel_0.15.0/default:toolchain
+build --action_env=BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1
+# Platform flags:
+# The toolchain container used for execution is defined in the target indicated
+# by "extra_execution_platforms", "host_platform" and "platforms".
+# If you are using your own toolchain container, you need to create a platform
+# target with "constraint_values" that allow for the toolchain specified with
+# "extra_toolchains" to be selected (given constraints defined in
+# "exec_compatible_with").
+# More about platforms: https://docs.bazel.build/versions/master/platforms.html
+build --extra_toolchains=@bazel_toolchains//configs/ubuntu16_04_clang/1.0/bazel_0.15.0/cpp:cc-toolchain-clang-x86_64-default
+build --extra_execution_platforms=//tools:rbe_ubuntu1604-angular
+build --host_platform=//tools:rbe_ubuntu1604-angular
+build --platforms=//tools:rbe_ubuntu1604-angular
+
+# Set various strategies so that all actions execute remotely. Mixing remote
+# and local execution will lead to errors unless the toolchain and remote
+# machine exactly match the host machine.
+build --spawn_strategy=remote
+build --strategy=Javac=remote
+build --strategy=Closure=remote
+build --genrule_strategy=remote
+build --define=EXECUTOR=remote
+
+# Enable the remote cache so action results can be shared across machines,
+# developers, and workspaces.
+build --remote_cache=remotebuildexecution.googleapis.com
+
+# Enable remote execution so actions are performed on the remote systems.
+build --remote_executor=remotebuildexecution.googleapis.com
+
+# Remote instance.
+build --remote_instance_name=projects/internal-200822/instances/default_instance
+
+# Enable encryption.
+build --tls_enabled=true
+
+# Enforce stricter environment rules, which eliminates some non-hermetic
+# behavior and therefore improves both the remote cache hit rate and the
+# correctness and repeatability of the build.
+build --experimental_strict_action_env=true
+
+# Set a higher timeout value, just in case.
+build --remote_timeout=3600
+
+# Enable authentication. This will pick up application default credentials by
+# default. You can use --auth_credentials=some_file.json to use a service
+# account credential instead.
+build --auth_enabled=true
+
+# Do not accept remote cache.
+build --remote_accept_cached=false

.devcontainer/README.md

@@ -1,31 +0,0 @@
-# VSCode Remote Development - Developing inside a Container
-
-This folder contains configuration files that can be used to opt into working on this repository in a [Docker container](https://www.docker.com/resources/what-container) via [VSCode](https://code.visualstudio.com/)'s Remote Development feature (see below).
-
-Info on remote development and developing inside a container with VSCode:
-- [VSCode: Remote Development](https://code.visualstudio.com/docs/remote/remote-overview)
-- [VSCode: Developing inside a Container](https://code.visualstudio.com/docs/remote/containers)
-- [VSCode: Remote Development FAQ](https://code.visualstudio.com/docs/remote/faq)
-
-
-## Usage
-
-_Prerequisite: [Install Docker](https://docs.docker.com/install) on your local environment._
-
-To get started, read and follow the instructions in [Developing inside a Container](https://code.visualstudio.com/docs/remote/containers). The [.devcontainer/](.) directory contains pre-configured `devcontainer.json` and `Dockerfile` files, which you can use to set up remote development with a docker container.
-
-In a nutshell, you need to:
-- Install the [Remote - Containers](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) extension.
-- Copy [recommended-Dockerfile](./recommended-Dockerfile) to `Dockerfile` (and optionally tweak to suit your needs).
-- Copy [recommended-devcontainer.json](./recommended-devcontainer.json) to `devcontainer.json` (and optionally tweak to suit your needs).
-- Open VSCode and bring up the [Command Palette](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette).
-- Type `Remote-Containers: Open Folder in Container` and choose your local clone of [angular/angular](https://github.com/angular/angular).
-
-The `.devcontainer/devcontainer.json` and `.devcontainer/Dockerfile` files are ignored by git, so you can have your own local versions. We may occasionally update the template files ([recommended-devcontainer.json](./recommended-devcontainer.json), [recommended-Dockerfile](./recommended-Dockerfile)), in which case you will need to manually update your local copies (if desired).
-
-
-## Updating `recommended-devcontainer.json` and `recommended-Dockerfile`
-
-You can update and commit the recommended config files (which people use as basis for their local configs), if you find that something is broken, out-of-date or can be improved.
-
-Please, keep in mind that any changes you make will potentially be used by many people on different environments. Try to keep these config files cross-platform compatible and free of personal preferences.

.devcontainer/recommended-Dockerfile

@@ -1,24 +0,0 @@
-# Image metadata and config.
-# Ideally, the Node.js version should match what we use on CI.
-# See `executors > default-executor` in `.circleci/config.yml`.
-FROM cimg/node:18.13.0@sha256:45d0ee279f522c4562a464df71108104cc9b2187205333ffd0707d4f05589731
-
-
-LABEL name="Angular dev environment" \
-      description="This image can be used to create a dev environment for building Angular." \
-      vendor="angular" \
-      version="1.0"
-
-EXPOSE 4000 4200 4433 5000 8080 9876
-
-
-# Switch to `root` (CircleCI images use `circleci` as the user).
-USER root
-
-
-# Configure `Node.js`/`npm`.
-RUN npm config --global set user root
-
-
-# Go! (And keep going.)
-CMD ["tail", "--follow", "/dev/null"]

.devcontainer/recommended-devcontainer.json

@@ -1,11 +0,0 @@
-// Reference: https://code.visualstudio.com/docs/remote/containers#_devcontainerjson-reference
-{
-  "name": "Angular dev container",
-  "dockerFile": "Dockerfile",
-  "appPort": [4000, 4200, 4433, 5000, 8080, 9876],
-  "postCreateCommand": "yarn install",
-  "extensions": [
-    "devondcarew.bazel-code",
-    "ms-vscode.vscode-typescript-tslint-plugin"
-  ],
-}

.editorconfig

@@ -1,4 +1,4 @@
-# https://editorconfig.org
+# http://editorconfig.org
 
 root = true
 

.gitattributes

@@ -4,3 +4,6 @@
 # JS and TS files must always use LF for tools to work
 *.js eol=lf
 *.ts eol=lf
+
+# Must keep Windows line ending to be parsed correctly
+scripts/windows/packages.txt eol=crlf

.github/ISSUE_TEMPLATE.md

@@ -1,6 +1,59 @@
-Please help us process issues more efficiently by filing an
-issue using one of the following templates:
+<!--
+PLEASE HELP US PROCESS GITHUB ISSUES FASTER BY PROVIDING THE FOLLOWING INFORMATION.
 
-https://github.com/angular/angular/issues/new/choose
+ISSUES MISSING IMPORTANT INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION.
+-->
 
-Thank you!
+## I'm submitting a...
+<!-- Check one of the following options with "x" -->
+<pre><code>
+[ ] Regression (a behavior that used to work and stopped working in a new release)
+[ ] Bug report  <!-- Please search GitHub for a similar issue or PR before submitting -->
+[ ] Performance issue
+[ ] Feature request
+[ ] Documentation issue or request
+[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
+[ ] Other... Please describe:
+</code></pre>
+
+## Current behavior
+<!-- Describe how the issue manifests. -->
+
+
+## Expected behavior
+<!-- Describe what the desired behavior would be. -->
+
+
+## Minimal reproduction of the problem with instructions
+<!--
+For bug reports please provide the *STEPS TO REPRODUCE* and if possible a *MINIMAL DEMO* of the problem via
+https://stackblitz.com or similar (you can use this template as a starting point: https://stackblitz.com/fork/angular-gitter).
+-->
+
+## What is the motivation / use case for changing the behavior?
+<!-- Describe the motivation or the concrete use case. -->
+
+
+## Environment
+
+<pre><code>
+Angular version: X.Y.Z
+<!-- Check whether this is still an issue in the most recent Angular version -->
+
+Browser:
+- [ ] Chrome (desktop) version XX
+- [ ] Chrome (Android) version XX
+- [ ] Chrome (iOS) version XX
+- [ ] Firefox version XX
+- [ ] Safari (desktop) version XX
+- [ ] Safari (iOS) version XX
+- [ ] IE version XX
+- [ ] Edge version XX
+ 
+For Tooling issues:
+- Node version: XX  <!-- run `node --version` -->
+- Platform:  <!-- Mac, Linux, Windows -->
+
+Others:
+<!-- Anything else relevant?  Operating system version, IDE, package manager, HTTP server, ... -->
+</code></pre>

.github/ISSUE_TEMPLATE/1-bug-report.yaml

@@ -1,86 +0,0 @@
-name: Bug Report
-description: Report a bug in the Angular Framework
-
-body:
-  - type: dropdown
-    id: affected-packages
-    attributes:
-      label: Which @angular/* package(s) are the source of the bug?
-      options:
-        - animations
-        - bazel
-        - common
-        - compiler-cli
-        - compiler
-        - core
-        - elements
-        - forms
-        - language-service
-        - localize
-        - platform-browser-dynamic
-        - platform-browser
-        - platform-server
-        - router
-        - service-worker
-        - upgrade
-        - zone.js
-        - Don't known / other
-      multiple: true
-    validations:
-      required: true
-
-  - type: dropdown
-    id: is-regression
-    attributes:
-      label: Is this a regression?
-      options:
-        - 'Yes'
-        - 'No'
-    validations:
-      required: true
-
-  - type: textarea
-    id: description
-    attributes:
-      label: Description
-    validations:
-      required: true
-
-  - type: input
-    id: reproduction
-    attributes:
-      label: Please provide a link to a minimal reproduction of the bug
-
-  - type: textarea
-    id: exception-or-error
-    attributes:
-      label: Please provide the exception or error you saw
-      render: true
-
-  - type: textarea
-    id: environment
-    attributes:
-      label: Please provide the environment you discovered this bug in (run `ng version`)
-      render: true
-      placeholder: |
-        Angular CLI: 12.0.5
-        Node: 14.17.0
-        Package Manager: yarn 1.22.10
-        OS: linux x64
-
-        Angular: 12.0.5
-        ... animations, cli, common, compiler, compiler-cli, core, forms
-        ... platform-browser, platform-browser-dynamic, router
-
-        Package                         Version
-        ---------------------------------------------------------
-        @angular-devkit/architect       0.1200.5
-        @angular-devkit/build-angular   12.0.5
-        @angular-devkit/core            12.0.5
-        rxjs                            6.6.7
-        typescript                      4.2.4
-
-  - type: textarea
-    id: other
-    attributes:
-      label: Anything else?

.github/ISSUE_TEMPLATE/2-feature-request.yaml

@@ -1,47 +0,0 @@
-name: 'Feature Request'
-description: Suggest a feature for Angular Framework
-
-body:
-  - type: dropdown
-    id: affected-packages
-    attributes:
-      label: Which @angular/* package(s) are relevant/related to the feature request?
-      options:
-        - animations
-        - bazel
-        - common
-        - compiler-cli
-        - compiler
-        - core
-        - elements
-        - forms
-        - language-service
-        - localize
-        - platform-browser-dynamic
-        - platform-browser
-        - platform-server
-        - router
-        - service-worker
-        - upgrade
-      multiple: true
-
-  - type: textarea
-    id: description
-    attributes:
-      label: Description
-    validations:
-      required: true
-
-  - type: textarea
-    id: proposed-solution
-    attributes:
-      label: Proposed solution
-    validations:
-      required: true
-
-  - type: textarea
-    id: alternatives-considered
-    attributes:
-      label: Alternatives considered
-    validations:
-      required: true

.github/ISSUE_TEMPLATE/3-docs-bug.yaml

@@ -1,58 +0,0 @@
-name: 'Docs or angular.dev Bug Report'
-description: Report an issue in Angular's documentation or angular.dev application
-
-body:
-  - type: textarea
-    id: description
-    attributes:
-      label: Describe the problem that you experienced
-    validations:
-      required: true
-
-  - type: input
-    id: affected-url
-    attributes:
-      label: Enter the URL of the topic with the problem
-
-  - type: textarea
-    id: documentation-goal
-    attributes:
-      label: Describe what you were looking for in the documentation
-
-  - type: textarea
-    id: reproduction-steps
-    attributes:
-      label: Describe the actions that led you to experience the problem
-
-  - type: textarea
-    id: expected-vs-actual-behavior
-    attributes:
-      label: Describe what you want to experience that would fix the problem
-
-  - type: textarea
-    id: screenshot
-    attributes:
-      label: Add a screenshot if that helps illustrate the problem
-
-  - type: textarea
-    id: exception-or-error
-    attributes:
-      label: If this problem caused an exception or error, please paste it here
-      render: true
-      placeholder: |
-        ```
-        Paste the exception or error here inside a markdown code block,
-        which is annotated by three grave \(`\) characters before and after the text block.
-        ```
-
-  - type: textarea
-    id: browser-info
-    attributes:
-      label: If the problem is browser-specific, please specify the device, OS, browser, and version
-      render: true
-
-  - type: textarea
-    id: additional-info
-    attributes:
-      label: Provide any additional information here in as much as detail as you can
-      render: true

.github/ISSUE_TEMPLATE/4-devtools.yaml

@@ -1,54 +0,0 @@
-name: 'Angular DevTools'
-description: Report an issue or suggest a feature for Angular DevTools
-
-body:
-  - type: checkboxes
-    id: bug-report-or-feature-request
-    attributes:
-      label: Is this a bug report or a feature request?
-      description: Select one.
-      options:
-        - label: Bug Report
-        - label: Feature Request
-
-  - type: textarea
-    id: reproduction-steps
-    attributes:
-      label: Please provide the steps to reproduce the issue [Bug Report only]
-
-  - type: textarea
-    id: expected-vs-actual-behavior
-    attributes:
-      label: Please provide the expected behavior vs the actual behavior you encountered [Bug Report only]
-
-  - type: textarea
-    id: screenshot
-    attributes:
-      label: Please provide a screenshot if possible [Bug Report only]
-
-  - type: textarea
-    id: exception-or-error
-    attributes:
-      label: Please provide the exception or error you saw [Bug Report only]
-      render: true
-
-  - type: textarea
-    id: browser-info
-    attributes:
-      label: Is this a browser-specific issue? If so, please specify the device, browser, and version. [Bug Report only]
-      render: true
-
-  - type: textarea
-    id: description
-    attributes:
-      label: Description [Feature Request only]
-
-  - type: textarea
-    id: proposed-solution
-    attributes:
-      label: Proposed solution [Feature Request only]
-
-  - type: textarea
-    id: alternatives-considered
-    attributes:
-      label: Alternatives considered [Feature Request only]

.github/ISSUE_TEMPLATE/config.yml

@@ -1,14 +0,0 @@
-blank_issues_enabled: false
-contact_links:
-  - name: Security issue disclosure
-    url: https://angular.dev/best-practices/security#report-issues
-    about: Report a security issue in Angular Framework, CDK, Material, or CLI
-  - name: Angular CLI
-    url: https://github.com/angular/angular-cli/issues/new/choose
-    about: Issues and feature requests for Angular CLI
-  - name: Angular Material and Components Development Kit (CDK)
-    url: https://github.com/angular/components/issues/new/choose
-    about: Issues and feature requests for Angular Material
-  - name: Support Request
-    url: https://github.com/angular/angular/blob/main/CONTRIBUTING.md#question
-    about: Questions and requests for support

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,7 +1,7 @@
 ## PR Checklist
 Please check if your PR fulfills the following requirements:
 
-- [ ] The commit message follows our guidelines: https://github.com/angular/angular/blob/main/CONTRIBUTING.md#commit
+- [ ] The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit
 - [ ] Tests for the changes have been added (for bug fixes / features)
 - [ ] Docs have been added / updated (for bug fixes / features)
 
@@ -10,17 +10,17 @@ Please check if your PR fulfills the following requirements:
 What kind of change does this PR introduce?
 
 <!-- Please check the one that applies to this PR using "x". -->
-
-- [ ] Bugfix
-- [ ] Feature
-- [ ] Code style update (formatting, local variables)
-- [ ] Refactoring (no functional changes, no api changes)
-- [ ] Build related changes
-- [ ] CI related changes
-- [ ] Documentation content changes
-- [ ] angular.dev application / infrastructure changes
-- [ ] Other... Please describe:
-
+```
+[ ] Bugfix
+[ ] Feature
+[ ] Code style update (formatting, local variables)
+[ ] Refactoring (no functional changes, no api changes)
+[ ] Build related changes
+[ ] CI related changes
+[ ] Documentation content changes
+[ ] angular.io application / infrastructure changes
+[ ] Other... Please describe:
+```
 
 ## What is the current behavior?
 <!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
@@ -32,10 +32,10 @@ Issue Number: N/A
 
 
 ## Does this PR introduce a breaking change?
-
-- [ ] Yes
-- [ ] No
-
+```
+[ ] Yes
+[ ] No
+```
 
 <!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. -->
 

.github/actions/deploy-docs-site/BUILD.bazel

@@ -1,18 +0,0 @@
-load("//tools:defaults.bzl", "esbuild_checked_in")
-
-exports_files([
-    "tsconfig.json",
-])
-
-esbuild_checked_in(
-    name = "main",
-    entry_point = "//.github/actions/deploy-docs-site/lib:main.ts",
-    external = [
-        "undici",
-    ],
-    platform = "node",
-    target = "node14",
-    deps = [
-        "//.github/actions/deploy-docs-site/lib",
-    ],
-)

.github/actions/deploy-docs-site/action.yml

@@ -1,19 +0,0 @@
-name: 'Deploy angular.dev site'
-description: 'Automatically deploy and set up redirects for angular.dev'
-author: 'Angular'
-inputs:
-  serviceKey:
-    description: 'The service key used for firebase deployments.'
-    required: true
-  githubReleaseTrainReadToken:
-    description: 'GitHub access token for reading release trains without rate limits.'
-    required: true
-  configPath:
-    description: 'The path to the firebase config file.'
-    required: true
-  distDir:
-    description: 'The path to the firebase dist directory.'
-    required: true
-runs:
-  using: 'node20'
-  main: 'main.js'

.github/actions/deploy-docs-site/lib/BUILD.bazel

@@ -1,23 +0,0 @@
-load("//tools:defaults.bzl", "ts_library")
-
-package(default_visibility = ["//.github/actions/deploy-docs-site:__subpackages__"])
-
-exports_files([
-    "main.ts",
-])
-
-ts_library(
-    name = "lib",
-    srcs = glob(
-        ["*.ts"],
-    ),
-    #tsconfig = "//.github/actions/deploy-docs-site:tsconfig.json",
-    deps = [
-        "@npm//@actions/core",
-        "@npm//@actions/github",
-        "@npm//@angular/ng-dev",
-        "@npm//@types/node",
-        "@npm//@types/tmp",
-        "@npm//tmp",
-    ],
-)

.github/actions/deploy-docs-site/lib/credential.ts

@@ -1,20 +0,0 @@
-import {fileSync} from 'tmp';
-import {writeSync} from 'fs';
-import {getInput, setSecret} from '@actions/core';
-
-let credentialFilePath: undefined | string;
-
-export function getCredentialFilePath(): string {
-  if (credentialFilePath === undefined) {
-    const tmpFile = fileSync({postfix: '.json'});
-    writeSync(tmpFile.fd, getInput('serviceKey', {required: true}));
-    setSecret(tmpFile.name);
-    credentialFilePath = tmpFile.name;
-  }
-  return credentialFilePath;
-}
-
-/** Github access token. Used for querying the active release trains. */
-export const githubReleaseTrainReadToken: string = getInput('githubReleaseTrainReadToken', {
-  required: true,
-});

.github/actions/deploy-docs-site/lib/deploy.ts

@@ -1,116 +0,0 @@
-import {cp, mkdtemp, readFile, rm, writeFile} from 'fs/promises';
-import {Deployment} from './deployments';
-import {join} from 'path';
-
-import {tmpdir} from 'os';
-import {spawnSync} from 'child_process';
-import {getCredentialFilePath} from './credential';
-
-export async function deployToFirebase(
-  deployment: Deployment,
-  configPath: string,
-  distDirPath: string,
-) {
-  if (deployment.destination == undefined) {
-    console.log(`No deployment necessary for docs created from: ${deployment.branch}`);
-    return;
-  }
-
-  console.log('Preparing for deployment to firebase...');
-
-  const tmpDeployDir = await mkdtemp(join(tmpdir(), 'deploy-directory'));
-  const deployConfigPath = join(tmpDeployDir, 'firebase.json');
-
-  const config = JSON.parse(await readFile(configPath, {encoding: 'utf-8'})) as {
-    hosting: {public: string};
-  };
-  config['hosting']['public'] = './dist';
-
-  await writeFile(deployConfigPath, JSON.stringify(config, null, 2));
-
-  await cp(distDirPath, join(tmpDeployDir, 'dist'), {recursive: true});
-  spawnSync(`chmod 777 -R ${tmpDeployDir}`, {encoding: 'utf-8', shell: true});
-
-  firebase(
-    `target:clear --config ${deployConfigPath} --project angular-dev-site hosting angular-docs`,
-    tmpDeployDir,
-  );
-  firebase(
-    `target:apply --config ${deployConfigPath} --project angular-dev-site hosting angular-docs ${deployment.destination}`,
-    tmpDeployDir,
-  );
-  firebase(
-    `deploy --config ${deployConfigPath} --project angular-dev-site --only hosting --non-interactive`,
-    tmpDeployDir,
-  );
-  firebase(
-    `target:clear --config ${deployConfigPath} --project angular-dev-site hosting angular-docs`,
-    tmpDeployDir,
-  );
-
-  await rm(tmpDeployDir, {recursive: true});
-}
-
-export async function setupRedirect(deployment: Deployment) {
-  if (deployment.redirect === undefined) {
-    console.log(`No redirect necessary for docs created from: ${deployment.branch}`);
-    return;
-  }
-
-  console.log('Preparing to set up redirect on firebase...');
-
-  const redirectConfig = JSON.stringify(
-    {
-      hosting: {
-        target: 'angular-docs',
-        redirects: [
-          {
-            type: 302,
-            regex: '^(.*)$',
-            destination: `${deployment.redirect.to}:1`,
-          },
-        ],
-      },
-    },
-    null,
-    2,
-  );
-
-  const tmpRedirectDir = await mkdtemp(join(tmpdir(), 'redirect-directory'));
-  const redirectConfigPath = join(tmpRedirectDir, 'firebase.json');
-
-  await writeFile(redirectConfigPath, redirectConfig);
-  spawnSync(`chmod 777 -R ${tmpRedirectDir}`, {encoding: 'utf-8', shell: true});
-
-  firebase(
-    `target:clear --config ${redirectConfigPath} --project angular-dev-site hosting angular-docs`,
-    tmpRedirectDir,
-  );
-  firebase(
-    `target:apply --config ${redirectConfigPath} --project angular-dev-site hosting angular-docs ${deployment.redirect.from}`,
-    tmpRedirectDir,
-  );
-  firebase(
-    `deploy --config ${redirectConfigPath} --project angular-dev-site --only hosting --non-interactive`,
-    tmpRedirectDir,
-  );
-  firebase(
-    `target:clear --config ${redirectConfigPath} --project angular-dev-site hosting angular-docs`,
-    tmpRedirectDir,
-  );
-
-  await rm(tmpRedirectDir, {recursive: true});
-}
-
-function firebase(cmd: string, cwd?: string) {
-  spawnSync('npx', `-y firebase-tools@13.15.1 ${cmd}`.split(' '), {
-    cwd,
-    encoding: 'utf-8',
-    shell: true,
-    stdio: 'inherit',
-    env: {
-      ...process.env,
-      GOOGLE_APPLICATION_CREDENTIALS: getCredentialFilePath(),
-    },
-  });
-}

.github/actions/deploy-docs-site/lib/deployments.ts

@@ -1,67 +0,0 @@
-import {fetchLongTermSupportBranchesFromNpm, ActiveReleaseTrains} from '@angular/ng-dev';
-import {ReleaseConfig} from '@angular/ng-dev';
-import {AuthenticatedGitClient} from '@angular/ng-dev';
-
-export interface Deployment {
-  branch: string;
-  redirect?: {
-    from: string;
-    to: string;
-  };
-  destination?: string;
-}
-
-export type Deployments = Map<string, Deployment>;
-
-export async function getDeployments(): Promise<Deployments> {
-  const {github} = await AuthenticatedGitClient.get();
-  const releaseTrains = await ActiveReleaseTrains.fetch({
-    api: github,
-    name: 'angular',
-    owner: 'angular',
-    nextBranchName: 'main',
-  });
-  const ltsBranches = await fetchLongTermSupportBranchesFromNpm({
-    representativeNpmPackage: '@angular/core',
-  } as ReleaseConfig);
-
-  const docSites = new Map<string, Deployment>();
-
-  [...ltsBranches.active, ...ltsBranches.inactive].forEach((branch) => {
-    docSites.set(branch.name, {
-      branch: branch.name,
-      destination: `v${branch.version.major}-angular-dev`,
-    });
-  });
-
-  docSites.set(releaseTrains.latest.branchName, {
-    branch: releaseTrains.latest.branchName,
-    redirect: {
-      from: `v${releaseTrains.latest.version.major}-angular-dev`,
-      to: 'https://angular.dev',
-    },
-    destination: 'angular-dev-site',
-  });
-
-  if (releaseTrains.releaseCandidate) {
-    docSites.set(releaseTrains.next.branchName, {
-      branch: releaseTrains.next.branchName,
-    });
-
-    docSites.set(releaseTrains.releaseCandidate.branchName, {
-      branch: releaseTrains.releaseCandidate.branchName,
-      destination: 'next-angular-dev',
-      redirect: {
-        from: `v${releaseTrains.releaseCandidate.version.major}-angular-dev`,
-        to: 'https://next.angular.dev',
-      },
-    });
-  } else {
-    docSites.set(releaseTrains.next.branchName, {
-      branch: releaseTrains.next.branchName,
-      destination: 'next-angular-dev',
-    });
-  }
-
-  return docSites;
-}

.github/actions/deploy-docs-site/lib/main.ts

@@ -1,75 +0,0 @@
-import {getInput, setFailed} from '@actions/core';
-import {context} from '@actions/github';
-import {deployToFirebase, setupRedirect} from './deploy';
-import {getDeployments} from './deployments';
-import {AuthenticatedGitClient, GithubConfig, setConfig} from '@angular/ng-dev';
-import {githubReleaseTrainReadToken} from './credential';
-
-const refMatcher = /refs\/heads\/(.*)/;
-
-async function deployDocs() {
-  setConfig({
-    github: <GithubConfig>{
-      mainBranchName: 'main',
-      name: 'angular',
-      owner: 'angular',
-    },
-  });
-
-  AuthenticatedGitClient.configure(githubReleaseTrainReadToken);
-
-  if (context.eventName !== 'push') {
-    throw Error();
-  }
-  const matchedRef = context.ref.match(refMatcher);
-  if (matchedRef === null) {
-    throw Error();
-  }
-
-  const currentBranch = matchedRef[1];
-  const configPath = getInput('configPath');
-  const distDir = getInput('distDir');
-
-  const deployment = (await getDeployments()).get(currentBranch);
-  if (deployment === undefined) {
-    console.log(`Current branch (${currentBranch}) does not deploy a documentation site.`);
-    console.log(`Exiting...`);
-    process.exit(0);
-  }
-
-  console.log('Doc site deployment information');
-  console.log('');
-  console.log('Current Branch:');
-  console.log(`  ${deployment.branch}`);
-  console.log('');
-  console.log('Firebase Site:');
-  if (deployment.destination === undefined) {
-    console.log('  No deployment of a documenation site is necessary');
-  } else {
-    console.log(`  Deploying to: ${deployment.destination}`);
-  }
-  console.log('');
-  console.log('Redirect Configuration:');
-  if (deployment.redirect === undefined) {
-    console.log('  No redirects are necessary');
-  } else {
-    console.log(`  From: ${deployment.redirect.from}`);
-    console.log(`  To: ${deployment.redirect.to}`);
-  }
-
-  await deployToFirebase(deployment, configPath, distDir);
-  await setupRedirect(deployment);
-}
-
-// Only run if the action is executed in a repository with is in the Angular org. This is in place
-// to prevent the action from actually running in a fork of a repository with this action set up.
-if (context.repo.owner === 'angular') {
-  deployDocs().catch((e: Error) => {
-    setFailed(e.message);
-    console.error(e);
-  });
-} else {
-  console.warn(
-    'The action was skipped as this action is only meant to run in repos belonging to the Angular organization.',
-  );
-}

.github/actions/deploy-docs-site/package.json

@@ -1,3 +0,0 @@
-{
-  "type": "module"
-}

.github/actions/deploy-docs-site/tsconfig.json

@@ -1,19 +0,0 @@
-{
-  "compilerOptions": {
-    "module": "Node16",
-    "target": "es2020",
-    "lib": ["es2021", "dom"],
-    "experimentalDecorators": true,
-    "strict": true,
-    "outDir": "../../../dist/tsc-non-bazel-out",
-    "skipLibCheck": true,
-    "noImplicitOverride": true,
-    // TODO(ESM): Remove this when Bazel also uses the Node resolution.
-    "esModuleInterop": true,
-    "noImplicitReturns": true,
-    "jsx": "react",
-    "jsxFactory": "h",
-    "jsxFragmentFactory": "Fragment"
-  },
-  "exclude": []
-}

.github/actions/saucelabs-legacy/action.yml

@@ -1,45 +0,0 @@
-name: 'Saucelabs legacy test job'
-description: 'Runs tests against Saucelabs (outside of Bazel)'
-
-runs:
-  using: 'composite'
-  steps:
-    - name: Setup Bazel
-      uses: angular/dev-infra/github-actions/bazel/setup@1f047e7dbae43ea969c2cafb53b33207e86b800f
-    - name: Setup Saucelabs Variables
-      uses: angular/dev-infra/github-actions/saucelabs@1f047e7dbae43ea969c2cafb53b33207e86b800f
-    - name: Starting Saucelabs tunnel service
-      shell: bash
-      run: ./tools/saucelabs/sauce-service.sh run &
-    # Build test fixtures for a test that rely on Bazel-generated fixtures. Note that disabling
-    # specific tests which are reliant on such generated fixtures is not an option as SystemJS
-    # in the Saucelabs legacy job always fetches referenced files, even if the imports would be
-    # guarded by an check to skip in the Saucelabs legacy job. We should be good running such
-    # test in all supported browsers on Saucelabs anyway until this job can be removed.
-    - name: Preparing Bazel-generated fixtures required in legacy tests
-      shell: bash
-      run: |
-        yarn bazel build //packages/core/test:downleveled_es5_fixture //packages/common/locales
-        # Needed for the ES5 downlevel reflector test in `packages/core/test/reflection`.
-        mkdir -p dist/legacy-test-out/core/test/reflection/
-        cp dist/bin/packages/core/test/reflection/es5_downleveled_inheritance_fixture.js \
-          dist/legacy-test-out/core/test/reflection/es5_downleveled_inheritance_fixture.js
-        # Locale files are needed for i18n tests running within Saucelabs. These are added
-        # directly as sources so that the TypeScript compilation of `/packages/tsconfig.json`
-        # can succeed. Note that the base locale and currencies files are checked-in, so
-        # we do not need to re-generate those through Bazel.
-        mkdir -p packages/common/locales/extra
-        cp dist/bin/packages/common/locales/*.ts packages/common/locales
-        cp dist/bin/packages/common/locales/extra/*.ts packages/common/locales/extra
-    - name: Build bundle of tests to run on Saucelabs
-      shell: bash
-      run: node tools/legacy-saucelabs/build-saucelabs-test-bundle.mjs
-    - name: Wait and confirm Saucelabs tunnel has connected
-      shell: bash
-      run: ./tools/saucelabs/sauce-service.sh ready-wait
-    - name: Running tests on Saucelabs.
-      shell: bash
-      run: KARMA_WEB_TEST_MODE=SL_REQUIRED yarn karma start ./karma-js.conf.js --single-run
-    - name: Stop Saucelabs tunnel service
-      shell: bash
-      run: ./tools/saucelabs/sauce-service.sh stop

.github/actions/yarn-install/action.yml

@@ -1,17 +0,0 @@
-name: 'Installing Yarn dependencies'
-description: 'Installs the dependencies using Yarn'
-
-runs:
-  using: 'composite'
-  steps:
-    - uses: actions/cache@6849a6489940f00c2f30c0fb92c6274307ccb58a # v4
-      with:
-        path: |
-          ./node_modules/
-        # If just `WORKSPACE` or `yarn.lock` is changed, the most recent cache can be restored.
-        # See: https://docs.github.com/en/actions/guides/caching-dependencies-to-speed-up-workflows#example-using-the-cache-action.
-        key: v1-angular-main-deps-${{hashFiles('WORKSPACE')}}-${{hashFiles('yarn.lock')}}
-        restore-keys: v1-angular-main-deps-
-
-    - run: yarn install --frozen-lockfile --non-interactive
-      shell: bash

.github/angular-robot.yml

@@ -1,10 +1,10 @@
 # Configuration for angular-robot
 
-# options for the size plugin
+#options for the size plugin
 size:
-  disabled: true
+  disabled: false
   maxSizeIncrease: 2000
-  circleCiStatusName: 'ci/circleci: test'
+  circleCiStatusName: "ci/circleci: test"
 
 # options for the merge plugin
 merge:
@@ -13,68 +13,90 @@ merge:
     # set to true to disable
     disabled: false
     # the name of the status
-    context: 'ci/angular: merge status'
+    context: "ci/angular: merge status"
     # text to show when all checks pass
-    successText: 'All checks passed!'
+    successText: "All checks passed!"
     # text to show when some checks are failing
-    failureText: 'The following checks are failing:'
+    failureText: "The following checks are failing:"
 
   # the g3 status will be added to your pull requests if they include files that match the patterns
   g3Status:
     # set to true to disable
-    disabled: true
+    disabled: false
     # the name of the status
-    context: 'google3'
+    context: "google3"
     # text to show when the status is pending, {{PRNumber}} will be replaced by the PR number
-    pendingDesc: 'Googler: run g3sync presubmit {{PRNumber}}'
+    pendingDesc: "Googler: run g3sync presubmit {{PRNumber}}"
     # text to show when the status is success
-    successDesc: 'Does not affect google3'
+    successDesc: "Does not affect google3"
     # link to use for the details
-    url: 'http://go/angular/g3sync'
+    url: "http://go/angular-g3sync"
     # list of patterns to check for the files changed by the PR
+    # this list must be manually kept in sync with google3/third_party/javascript/angular2/copy.bara.sky
     include:
+      - "LICENSE"
+      - "modules/**"
+      - "packages/**"
+    # list of patterns to ignore for the files changed by the PR
     exclude:
+      - "packages/language-service/**"
+      - "**/.gitignore"
+      - "**/.gitkeep"
+      - "**/package.json"
+      - "**/tsconfig-build.json"
+      - "**/tsconfig.json"
+      - "**/rollup.config.js"
+      - "**/BUILD.bazel"
+      - "packages/**/integrationtest/**"
+      - "packages/**/test/**"
 
   # comment that will be added to a PR when there is a conflict, leave empty or set to false to disable
-  mergeConflictComment: "Hi @{{PRAuthor}}! This PR has merge conflicts due to recent upstream merges.\nPlease help to unblock it by resolving these conflicts. Thanks!"
+  mergeConflictComment: "Hi @{{PRAuthor}}! This PR has merge conflicts due to recent upstream merges.
+\nPlease help to unblock it by resolving these conflicts. Thanks!"
 
   # label to monitor
-  mergeLabel: 'action: merge'
-
-  # adding any of these labels will also add the merge label
-  mergeLinkedLabels:
-    - 'action: merge-assistance'
+  mergeLabel: "PR action: merge"
 
   # list of checks that will determine if the merge label can be added
   checks:
+
     # require that the PR has reviews from all requested reviewers
     #
     # This enables us to request reviews from both eng and tech writers, or multiple eng folks, and prevents accidental merges.
-    # Rather than merging PRs with pending reviews, if all approvals are obtained and additional reviews are not needed, any pending reviewers should be removed via GitHub UI (this also leaves an audit trail behind these decisions).
+    # Rather than merging PRs with pending reviews, if all PullApprove requirements are satisfied and additional reviews are not needed pending reviewers should be removed via GitHub UI (this also leaves an audit trail behind these decisions).
     requireReviews: true,
 
     # whether the PR shouldn't have a conflict with the base branch
     noConflict: true
-    # list of labels that a PR needs to have, checked with a regexp.
+    # list of labels that a PR needs to have, checked with a regexp (e.g. "PR target:" will work for the label "PR target: master")
     requiredLabels:
-      - 'target: *'
+      - "PR target: *"
+      - "cla: yes"
 
     # list of labels that a PR shouldn't have, checked after the required labels with a regexp
     forbiddenLabels:
-      - 'target: TBD'
-      - 'action: cleanup'
-      - 'action: review'
-      - 'state: blocked'
+      - "PR target: TBD"
+      - "PR action: cleanup"
+      - "PR action: review"
+      - "PR state: blocked"
+      - "cla: no"
 
     # list of PR statuses that need to be successful
     requiredStatuses:
-      - 'google-internal-tests'
-      - 'pullapprove'
+      - "continuous-integration/travis-ci/pr"
+      - "code-review/pullapprove"
+      - "ci/circleci: build"
+      - "ci/circleci: lint"
 
   # the comment that will be added when the merge label is added despite failing checks, leave empty or set to false to disable
   # {{MERGE_LABEL}} will be replaced by the value of the mergeLabel option
   # {{PLACEHOLDER}} will be replaced by the list of failing checks
-  mergeRemovedComment: "I see that you just added the `{{MERGE_LABEL}}` label, but the following checks are still failing:\n{{PLACEHOLDER}}\n\n**If you want your PR to be merged, it has to pass all the CI checks.**\n\nIf you can't get the PR to a green state due to flakes or broken `main`, please try rebasing to `main` and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help."
+  mergeRemovedComment: "I see that you just added the `{{MERGE_LABEL}}` label, but the following checks are still failing:
+\n{{PLACEHOLDER}}
+\n
+\n**If you want your PR to be merged, it has to pass all the CI checks.**
+\n
+\nIf you can't get the PR to a green state due to flakes or broken master, please try rebasing to master and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help."
 
 # options for the triage plugin
 triage:
@@ -84,48 +106,21 @@ triage:
   defaultMilestone: 82,
   # arrays of labels that determine if an issue has been triaged by the caretaker
   l1TriageLabels:
-    - - 'area: *'
+    -
+      - "comp: *"
   # arrays of labels that determine if an issue has been fully triaged
   l2TriageLabels:
-    - - 'P0'
-      - 'area: *'
-    - - 'P1'
-      - 'area: *'
-    - - 'P2'
-      - 'area: *'
-    - - 'P3'
-      - 'area: *'
-    - - 'P4'
-      - 'area: *'
-    - - 'P5'
-      - 'area: *'
-    - - 'feature'
-      - 'area: *'
-    - - 'discussion'
-      - 'area: *'
-    - - 'needs clarification'
-      - 'area: *'
-    - - 'needs reproduction'
-      - 'area: *'
-
-# options for the triage PR plugin
-triagePR:
-  # set to true to disable
-  disabled: false
-  # number of the milestone to apply when the PR has not been triaged yet
-  needsTriageMilestone: 83,
-  # number of the milestone to apply when the PR is triaged
-  defaultMilestone: 82,
-  # arrays of labels that determine if a PR has been triaged by the caretaker
-  l1TriageLabels:
-    - - 'area: *'
-  # arrays of labels that determine if a PR has been fully triaged
-  l2TriageLabels:
-    - - 'area: *'
-
-# options for rerunning CI
-rerunCircleCI:
-  # set to true to disable
-  disabled: false
-  # the label which when added triggers a rerun of the default CircleCI workflow
-  triggerRerunLabel: 'action: rerun CI at HEAD'
+    -
+      - "type: bug/fix"
+      - "severity*"
+      - "freq*"
+      - "comp: *"
+    -
+      - "type: feature"
+      - "comp: *"
+    -
+      - "type: refactor"
+      - "comp: *"
+    -
+      - "type: RFC / Discussion / question"
+      - "comp: *"

.github/workflows/adev-preview-build.yml

@@ -1,38 +0,0 @@
-# This workflow builds the previews for pull requests when a certain label is applied.
-# The actual deployment happens as part of a dedicated second workflow to avoid security
-# issues where the building would otherwise occur in an authorized context where secrets
-# could be leaked. More details can be found here:
-
-# https://securitylab.github.com/research/github-actions-preventing-pwn-requests/.
-
-name: Build adev for preview deployment
-
-on:
-  pull_request:
-    types: [synchronize, labeled]
-
-permissions: read-all
-
-jobs:
-  adev-build:
-    runs-on: ubuntu-latest
-    if: |
-      (github.event.action == 'labeled' && github.event.label.name == 'adev: preview') ||
-      (github.event.action == 'synchronize' && contains(github.event.pull_request.labels.*.name, 'adev: preview'))
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Setup Bazel RBE
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Install node modules
-        run: yarn install --frozen-lockfile
-      - name: Build adev to ensure it continues to work
-        run: yarn bazel build //adev:build --prerender_adev --config=release
-      - uses: angular/dev-infra/github-actions/previews/pack-and-upload-artifact@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          workflow-artifact-name: 'adev-preview'
-          pull-number: '${{github.event.pull_request.number}}'
-          artifact-build-revision: '${{github.event.pull_request.head.sha}}'
-          deploy-directory: './dist/bin/adev/build/browser'

.github/workflows/adev-preview-deploy.yml

@@ -1,50 +0,0 @@
-# This workflow runs whenever the ADEV build workflow has completed. Deployment happens
-# as part of a dedicated second workflow to avoid security issues where the building would
-# otherwise occur in an authorized context where secrets could be leaked.
-#
-# More details can be found here:
-# https://securitylab.github.com/research/github-actions-preventing-pwn-requests/.
-
-name: Deploying adev preview to Firebase
-
-on:
-  workflow_run:
-    workflows: ['Build adev for preview deployment']
-    types: [completed]
-
-permissions:
-  # Needed in order to be able to comment on the pull request.
-  pull-requests: write
-  # Needed in order to checkout the repository
-  contents: read
-  # Needed in order to retrieve the artifacts from the previous job
-  actions: read
-
-env:
-  PREVIEW_PROJECT: ng-dev-previews
-  PREVIEW_SITE: ng-dev-previews-fw
-
-jobs:
-  deploy:
-    runs-on: ubuntu-latest
-    if: ${{ github.event.workflow_run.conclusion == 'success' }}
-    steps:
-      - uses: actions/checkout@eef61447b9ff4aafe5dcd4e0bbf5d482be7e7871 # v4
-        with:
-          token: '${{secrets.GITHUB_TOKEN}}'
-
-      - name: Configure Firebase deploy target
-        working-directory: ./
-        run: |
-          # We can use `npx` as the Firebase deploy actions uses it too.
-          npx -y firebase-tools@latest target:clear --config adev/firebase.json --project ${{env.PREVIEW_PROJECT}} hosting angular-docs
-          npx -y firebase-tools@latest target:apply --config adev/firebase.json --project ${{env.PREVIEW_PROJECT}} hosting angular-docs ${{env.PREVIEW_SITE}}
-
-      - uses: angular/dev-infra/github-actions/previews/upload-artifacts-to-firebase@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          github-token: '${{secrets.GITHUB_TOKEN}}'
-          workflow-artifact-name: 'adev-preview'
-          firebase-config-dir: './adev'
-          firebase-public-dir: './adev/build/browser'
-          firebase-project-id: '${{env.PREVIEW_PROJECT}}'
-          firebase-service-key: '${{secrets.FIREBASE_PREVIEW_SERVICE_TOKEN}}'

.github/workflows/assistant-to-the-branch-manager.yml

@@ -1,21 +0,0 @@
-name: DevInfra
-
-on:
-  push:
-  pull_request_target:
-    types: [opened, synchronize, reopened, ready_for_review, labeled]
-
-# Declare default permissions as read only.
-permissions:
-  contents: read
-
-jobs:
-  assistant_to_the_branch_manager:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332 # v4.1.7
-        with:
-          persist-credentials: false
-      - uses: angular/dev-infra/github-actions/branch-manager@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          angular-robot-key: ${{ secrets.ANGULAR_ROBOT_PRIVATE_KEY }}

.github/workflows/benchmark-compare.yml

@@ -1,68 +0,0 @@
-name: Run benchmark comparison
-
-on:
-  issue_comment:
-    types: [created]
-
-permissions: read-all
-
-jobs:
-  benchmark-compare:
-    runs-on: ubuntu-latest
-    if: ${{ github.event.issue.pull_request && startsWith(github.event.comment.body, '/benchmark-compare ')}}
-    steps:
-      - uses: TheModdingInquisition/actions-team-membership@a69636a92bc927f32c3910baac06bacc949c984c # v1.0
-        with:
-          team: 'team'
-          organization: angular
-          token: ${{secrets.BENCHMARK_COMPARE_MEMBERSHIP_GITHUB_TOKEN}}
-          exit: true
-
-      # Indicate that the benchmark command was received.
-      - uses: peter-evans/create-or-update-comment@71345be0265236311c031f5c7866368bd1eff043 # v4
-        with:
-          comment-id: ${{github.event.comment.id}}
-          token: '${{secrets.BENCHMARK_POST_RESULTS_GITHUB_TOKEN}}'
-          reactions: 'rocket'
-
-      - uses: alessbell/pull-request-comment-branch@aad01d65d6982b8eacabed5e9a684cd8ceb98da6 # v1.1
-        id: comment-branch
-
-      - uses: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332 # v4.1.7
-        with:
-          # Specify repository as the PR branch might be from a fork.
-          repository: ${{steps.comment-branch.outputs.head_owner}}/${{steps.comment-branch.outputs.head_repo}}
-          # Checkout the pull request and assume it being trusted given we've checked
-          # that the action was triggered by a team member.
-          ref: ${{steps.comment-branch.outputs.head_ref}}
-
-      - uses: ./.github/actions/yarn-install
-
-      - uses: angular/dev-infra/github-actions/bazel/configure-remote@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          bazelrc: ./.bazelrc.user
-
-      - name: Preparing benchmark for GitHub action
-        id: info
-        env:
-          # Untrusted input used in an executable code, must be wrapped as an env var to prevent injections
-          COMMENT_BODY: ${{ github.event.comment.body }}
-        run: yarn benchmarks prepare-for-github-action "$COMMENT_BODY"
-
-      - run: yarn benchmarks run-compare ${{steps.info.outputs.compareSha}} ${{steps.info.outputs.benchmarkTarget}}
-        id: benchmark
-        name: Running benchmark
-
-      - uses: peter-evans/create-or-update-comment@71345be0265236311c031f5c7866368bd1eff043 # v4
-        with:
-          issue-number: ${{github.event.issue.number}}
-          token: '${{secrets.BENCHMARK_POST_RESULTS_GITHUB_TOKEN}}'
-          body: |
-            ## Benchmark Test Results
-            **Test**: `${{steps.info.outputs.benchmarkTarget}}`
-
-            ### PR (${{steps.info.outputs.prHeadSha}})
-            ${{steps.benchmark.outputs.workingStageResultsText}}
-
-            ### Compare Ref (${{steps.info.outputs.compareSha}})
-            ${{steps.benchmark.outputs.comparisonResultsText}}

.github/workflows/ci.yml

@@ -1,219 +0,0 @@
-name: CI (push)
-
-on:
-  push:
-    branches:
-      - main
-      - '[0-9]+.[0-9]+.x'
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: true
-
-permissions: {}
-
-defaults:
-  run:
-    shell: bash
-
-jobs:
-  lint:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          cache-node-modules: true
-      - name: Install node modules
-        run: yarn install --frozen-lockfile
-      - name: Check code lint
-        run: yarn -s tslint
-      - name: Check for circular dependencies
-        run: yarn -s ts-circular-deps:check
-      - name: Validate pull approve configuration
-        run: yarn -s ng-dev pullapprove verify
-      - name: Validate angular robot configuration
-        run: yarn -s ng-dev ngbot verify
-      - name: Confirm code builds with typescript as expected
-        run: yarn -s check-tooling-setup
-
-  devtools:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          cache-node-modules: true
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Setup Bazel RBE
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          google_credential: ${{ secrets.RBE_TRUSTED_BUILDS_USER }}
-      - name: Install node modules
-        run: yarn install --frozen-lockfile
-      - name: Run unit tests
-        run: yarn devtools:test
-      - name: Test build
-        run: yarn devtools:build:chrome
-
-  test:
-    runs-on: ubuntu-latest-4core
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          cache-node-modules: true
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Setup Bazel Remote Caching
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          google_credential: ${{ secrets.RBE_TRUSTED_BUILDS_USER }}
-      - name: Install node modules
-        run: yarn install --frozen-lockfile --network-timeout 100000
-      - name: Run CI tests for framework
-        run: yarn test:ci
-
-  integration-tests:
-    runs-on: ubuntu-latest-4core
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          cache-node-modules: true
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Setup Bazel Remote Caching
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          google_credential: ${{ secrets.RBE_TRUSTED_BUILDS_USER }}
-      - name: Install node modules
-        run: yarn install --frozen-lockfile --network-timeout 100000
-      - name: Run integration CI tests for framework
-        run: yarn integration-tests:ci
-
-  adev:
-    runs-on:
-      labels: ubuntu-latest-4core
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Setup Bazel RBE
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          google_credential: ${{ secrets.RBE_TRUSTED_BUILDS_USER }}
-      - name: Install node modules
-        run: yarn install --frozen-lockfile
-      - name: Build adev in fast mode to ensure it continues to work
-        run: yarn bazel build //adev:build --config=release
-      # TODO: re-enable tests once the next release is shipped
-      # Tests are broken because of https://github.com/angular/angular/issues/54858
-      # - name: Run tests
-      # run: yarn bazel test //adev/...
-
-  publish-snapshots:
-    runs-on:
-      labels: ubuntu-latest
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          cache-node-modules: true
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Setup Bazel RBE
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          google_credential: ${{ secrets.RBE_TRUSTED_BUILDS_USER }}
-      - name: Install node modules
-        run: yarn install --frozen-lockfile
-      - run: echo "https://${{secrets.SNAPSHOT_BUILDS_GITHUB_TOKEN}}:@github.com" > ${HOME}/.git_credentials
-      - run: yarn build
-      - run: ./scripts/ci/publish-build-artifacts.sh
-
-  zone-js:
-    runs-on:
-      labels: ubuntu-latest-4core
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          cache-node-modules: true
-          node-module-directories: |
-            ./node_modules
-            ./packages/zone.js/node_modules
-            ./packages/zone.js/test/typings/node_modules
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Setup Bazel RBE
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          google_credential: ${{ secrets.RBE_TRUSTED_BUILDS_USER }}
-      - name: Install node modules
-        run: yarn install --frozen-lockfile
-      - run: |
-          yarn bazel build \
-          //packages/zone.js/bundles:zone.umd.js \
-          //packages/zone.js:npm_package \
-          //packages/zone.js/test/closure:closure_js \
-
-      - run: |
-          rm -Rf packages/zone.js/build
-          rm -Rf packages/zone.js/test/extra/*.umd.js
-
-          mkdir -p packages/zone.js/build/
-          mkdir -p packages/zone.js/build/test/
-
-          cp dist/bin/packages/zone.js/bundles/zone.umd.js packages/zone.js/build/zone.umd.js
-          cp dist/bin/packages/zone.js/npm_package/bundles/zone-mix.umd.js ./packages/zone.js/test/extra/
-          cp dist/bin/packages/zone.js/npm_package/bundles/zone-patch-electron.umd.js ./packages/zone.js/test/extra/
-          cp dist/bin/packages/zone.js/test/closure/zone.closure.mjs ./packages/zone.js/build/test/zone.closure.mjs
-
-        # Install
-      - run: yarn --cwd packages/zone.js install --frozen-lockfile --non-interactive
-        # Run zone.js tools tests
-      - run: yarn --cwd packages/zone.js promisefinallytest
-      - run: yarn --cwd packages/zone.js jest:test
-      - run: yarn --cwd packages/zone.js jest:nodetest
-      - run: yarn --cwd packages/zone.js electrontest
-      - run: yarn --cwd packages/zone.js/test/typings install --frozen-lockfile --non-interactive
-      - run: yarn --cwd packages/zone.js/test/typings test
-
-  # saucelabs:
-  #   runs-on: ubuntu-latest-4core
-  #   env:
-  #     SAUCE_TUNNEL_IDENTIFIER: angular-framework-${{ github.run_number }}
-  #   steps:
-  #     - name: Initialize environment
-  #       uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@1f047e7dbae43ea969c2cafb53b33207e86b800f
-  #       with:
-  #         cache-node-modules: true
-  #     - name: Install node modules
-  #       run: yarn install --frozen-lockfile
-  #     - uses: ./.github/actions/saucelabs-legacy
-
-  adev-deploy:
-    needs: [adev]
-    if: needs.adev.result == 'success'
-    runs-on: ubuntu-latest
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Setup Bazel RBE
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Install node modules
-        run: yarn install --frozen-lockfile
-      - name: Build adev to ensure it continues to work
-        run: yarn bazel build //adev:build --prerender_adev --config=release
-      - name: Deploy to firebase
-        uses: ./.github/actions/deploy-docs-site
-        with:
-          serviceKey: ${{ secrets.ANGULAR_DEV_SITE_DEPLOY }}
-          githubReleaseTrainReadToken: ${{ secrets.DOCS_DEPLOY_GITHUB_RELEASE_TRAIN_TOKEN }}
-          configPath: 'adev/firebase.json'
-          distDir: 'dist/bin/adev/build/browser'

.github/workflows/dev-infra.yml

@@ -1,25 +0,0 @@
-name: DevInfra
-
-on:
-  pull_request_target:
-    types: [opened, synchronize, reopened]
-
-# Declare default permissions as read only.
-permissions:
-  contents: read
-
-jobs:
-  labels:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
-      - uses: angular/dev-infra/github-actions/pull-request-labeling@4b4659eabe75a67cebf4692c3c88a98275c67200
-        with:
-          angular-robot-key: ${{ secrets.ANGULAR_ROBOT_PRIVATE_KEY }}
-  post_approval_changes:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
-      - uses: angular/dev-infra/github-actions/post-approval-changes@4b4659eabe75a67cebf4692c3c88a98275c67200
-        with:
-          angular-robot-key: ${{ secrets.ANGULAR_ROBOT_PRIVATE_KEY }}

.github/workflows/google-internal-tests.yml

@@ -1,21 +0,0 @@
-name: Google Internal Tests Enforcement
-
-on:
-  pull_request_target:
-    types: [opened, reopened, synchronize]
-
-permissions: {}
-
-jobs:
-  trigger:
-    permissions:
-      pull-requests: read
-      statuses: write
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332 # v4.1.7
-      - uses: angular/dev-infra/github-actions/google-internal-tests@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          run-tests-guide-url: http://go/angular-g3sync-start
-          github-token: ${{ secrets.GITHUB_TOKEN }}
-          sync-config: ./.ng-dev/google-sync-config.json

.github/workflows/manual.yml

@@ -1,34 +0,0 @@
-name: Manual jobs
-
-on:
-  workflow_dispatch:
-    inputs: {}
-
-jobs:
-  # Bazel saucelabs job resides in `manual.yml` because it's currently unstable, but
-  # kept as "runnable" for debugging/stabilization effort purposes.
-  bazel-saucelabs:
-    runs-on: ubuntu-latest-4core
-    env:
-      JOBS: 2
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          cache-node-modules: true
-      - name: Install node modules
-        run: yarn install --frozen-lockfile
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Setup Bazel Remote Caching
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Setup Saucelabs Variables
-        uses: angular/dev-infra/github-actions/saucelabs@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Set up Sauce Tunnel Daemon
-        run: yarn bazel run //tools/saucelabs-daemon/background-service -- $JOBS &
-        env:
-          SAUCE_TUNNEL_IDENTIFIER: angular-framework-${{ github.run_number }}
-      - name: Run all saucelabs bazel tests
-        run: |
-          TESTS=$(./node_modules/.bin/bazelisk query --output label '(kind(karma_web_test, ...) intersect attr("tags", "saucelabs", ...)) except attr("tags", "fixme-saucelabs", ...)')
-          yarn bazel test --config=saucelabs --jobs=$JOBS ${TESTS}

.github/workflows/merge-ready-status.yml

@@ -1,14 +0,0 @@
-name: Merge Ready
-
-on: pull_request_target
-
-# Declare default permissions as read only.
-permissions: {}
-
-jobs:
-  status:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: angular/dev-infra/github-actions/unified-status-check@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          angular-robot-key: ${{ secrets.ANGULAR_ROBOT_PRIVATE_KEY }}

.github/workflows/pr.yml

@@ -1,195 +0,0 @@
-name: Pull Request
-
-on:
-  pull_request:
-    types: [opened, synchronize, reopened]
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: true
-
-permissions: {}
-
-defaults:
-  run:
-    shell: bash
-
-jobs:
-  lint:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          cache-node-modules: true
-      - name: Install node modules
-        run: yarn install --frozen-lockfile
-      - name: Check code lint
-        run: yarn -s tslint
-      - name: Check for circular dependencies
-        run: yarn -s ts-circular-deps:check
-      - name: Validate pull approve configuration
-        run: yarn -s ng-dev pullapprove verify
-      - name: Validate angular robot configuration
-        run: yarn -s ng-dev ngbot verify
-      - name: Confirm code builds with typescript as expected
-        run: yarn -s check-tooling-setup
-      - name: Check commit message
-        run: yarn ng-dev commit-message validate-range ${{ github.event.pull_request.base.sha }} ${{ github.event.pull_request.head.sha }}
-      - name: Check code format
-        run: yarn ng-dev format changed --check ${{ github.event.pull_request.base.sha }}
-      - name: Check Package Licenses
-        uses: angular/dev-infra/github-actions/linting/licenses@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          allow-dependencies-licenses: 'pkg:npm/google-protobuf@'
-
-  devtools:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          cache-node-modules: true
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Setup Bazel RBE
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Install node modules
-        run: yarn install --frozen-lockfile
-      - name: Run unit tests
-        run: yarn devtools:test
-      - name: Test build
-        run: yarn devtools:build:chrome
-
-  test:
-    runs-on: ubuntu-latest-8core
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          cache-node-modules: true
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Setup Bazel Remote Caching
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Install node modules
-        run: yarn install --frozen-lockfile --network-timeout 100000
-      - name: Run CI tests for framework
-        run: yarn test:ci
-
-  integration-tests:
-    runs-on: ubuntu-latest-4core
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          cache-node-modules: true
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Setup Bazel Remote Caching
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Install node modules
-        run: yarn install --frozen-lockfile --network-timeout 100000
-      - name: Run integration CI tests for framework
-        run: yarn integration-tests:ci
-
-  artifacts:
-    needs: [test]
-    if: needs.test.result == 'success'
-    runs-on: ubuntu-latest
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          cache-node-modules: true
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Setup Bazel Remote Caching
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Install node modules
-        run: yarn install --frozen-lockfile --network-timeout 100000
-      - name: Build artifacts
-        run: yarn tsx ./scripts/build/build-packages-dist.mts
-      - name: Archive build artifacts
-        uses: actions/upload-artifact@4cec3d8aa04e39d1a68397de0c4cd6fb9dce8ec1 # v4.6.1
-        with:
-          name: pr-artifacts-${{ github.event.number }}
-          path: dist/packages-dist/
-
-  adev:
-    runs-on:
-      labels: ubuntu-latest-8core
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Setup Bazel RBE
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Install node modules
-        run: yarn install --frozen-lockfile
-      - name: Build adev in fast mode to ensure it continues to work
-        run: yarn bazel build //adev:build --config=release
-      # TODO: re-enable tests once the next release is shipped
-      # Tests are broken because of https://github.com/angular/angular/issues/54858
-      # - name: Run tests
-      #  run: yarn bazel test //adev/...
-
-  zone-js:
-    runs-on:
-      labels: ubuntu-latest-4core
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          cache-node-modules: true
-          node-module-directories: |
-            ./node_modules
-            ./packages/zone.js/node_modules
-            ./packages/zone.js/test/typings/node_modules
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Setup Bazel RBE
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@1f047e7dbae43ea969c2cafb53b33207e86b800f
-      - name: Install node modules
-        run: yarn install --frozen-lockfile
-      - run: |
-          yarn bazel build \
-          //packages/zone.js/bundles:zone.umd.js \
-          //packages/zone.js:npm_package \
-          //packages/zone.js/test/closure:closure_js \
-
-      - run: |
-          rm -Rf packages/zone.js/build
-          rm -Rf packages/zone.js/test/extra/*.umd.js
-
-          mkdir -p packages/zone.js/build/
-          mkdir -p packages/zone.js/build/test/
-
-          cp dist/bin/packages/zone.js/bundles/zone.umd.js packages/zone.js/build/zone.umd.js
-          cp dist/bin/packages/zone.js/npm_package/bundles/zone-mix.umd.js ./packages/zone.js/test/extra/
-          cp dist/bin/packages/zone.js/npm_package/bundles/zone-patch-electron.umd.js ./packages/zone.js/test/extra/
-          cp dist/bin/packages/zone.js/test/closure/zone.closure.mjs ./packages/zone.js/build/test/zone.closure.mjs
-
-        # Install
-      - run: yarn --cwd packages/zone.js install --frozen-lockfile --non-interactive
-        # Run zone.js tools tests
-      - run: yarn --cwd packages/zone.js promisefinallytest
-      - run: yarn --cwd packages/zone.js jest:test
-      - run: yarn --cwd packages/zone.js jest:nodetest
-      - run: yarn --cwd packages/zone.js electrontest
-      - run: yarn --cwd packages/zone.js/test/typings install --frozen-lockfile --non-interactive
-      - run: yarn --cwd packages/zone.js/test/typings test
-
-  # saucelabs:
-  #   runs-on: ubuntu-latest-4core
-  #   env:
-  #     SAUCE_TUNNEL_IDENTIFIER: angular-framework-${{ github.run_number }}
-  #   steps:
-  #     - name: Initialize environment
-  #       uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@1f047e7dbae43ea969c2cafb53b33207e86b800f
-  #       with:
-  #         cache-node-modules: true
-  #     - name: Install node modules
-  #       run: yarn install --frozen-lockfile
-  #     - uses: ./.github/actions/saucelabs-legacy

.github/workflows/scorecard.yml

@@ -1,52 +0,0 @@
-name: OpenSSF Scorecard
-on:
-  branch_protection_rule:
-  schedule:
-    - cron: '0 0 * * 0'
-  push:
-    branches: [main]
-  workflow_dispatch:
-
-# Declare default permissions as read only.
-permissions:
-  contents: read
-
-jobs:
-  analysis:
-    name: Scorecards analysis
-    runs-on: ubuntu-latest
-    permissions:
-      # Needed to upload the results to code-scanning dashboard.
-      security-events: write
-      # Needed to publish results
-      id-token: write
-      actions: read
-      contents: read
-
-    steps:
-      - name: 'Checkout code'
-        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
-        with:
-          persist-credentials: false
-
-      - name: 'Run analysis'
-        uses: ossf/scorecard-action@62b2cac7ed8198b15735ed49ab1e5cf35480ba46 # v2.4.0
-        with:
-          results_file: results.sarif
-          results_format: sarif
-          repo_token: ${{ secrets.GITHUB_TOKEN }}
-          publish_results: true
-
-      # Upload the results as artifacts.
-      - name: 'Upload artifact'
-        uses: actions/upload-artifact@b4b15b8c7c6ac21ea08fcf65892d2ee8f75cf882 # v4.4.3
-        with:
-          name: SARIF file
-          path: results.sarif
-          retention-days: 5
-
-      # Upload the results to GitHub's code scanning dashboard.
-      - name: 'Upload to code-scanning'
-        uses: github/codeql-action/upload-sarif@9278e421667d5d90a2839487a482448c4ec7df4d # v3.27.2
-        with:
-          sarif_file: results.sarif

.github/workflows/update-cli-help.yml

@@ -1,44 +0,0 @@
-name: Update ADEV Angular CLI help
-
-on:
-  workflow_dispatch:
-    inputs: {}
-  push:
-    branches:
-      - 'main'
-      - '[0-9]+.[0-9]+.x'
-
-# Declare default permissions as read only.
-permissions:
-  contents: read
-
-jobs:
-  update_cli_help:
-    name: Update Angular CLI help (if necessary)
-    if: github.repository == 'angular/angular'
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout the repository
-        uses: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332 # v4.1.7
-        with:
-          # Setting `persist-credentials: false` prevents the github-action account from being the
-          # account that is attempted to be used for authentication, instead the remote is set to
-          # an authenticated URL.
-          persist-credentials: false
-          # This is needed as otherwise the PR creation will fail with `shallow update not allowed` when the forked branch is not in sync.
-          fetch-depth: 0
-      - name: Generate CLI help
-        run: node adev/scripts/update-cli-help/index.mjs
-        env:
-          ANGULAR_CLI_BUILDS_READONLY_GITHUB_TOKEN: ${{ secrets.ANGULAR_CLI_BUILDS_READONLY_GITHUB_TOKEN }}
-      - name: Create a PR (if necessary)
-        uses: angular/dev-infra/github-actions/create-pr-for-changes@1f047e7dbae43ea969c2cafb53b33207e86b800f
-        with:
-          branch-prefix: update-cli-help
-          pr-title: 'docs: update Angular CLI help [${{github.ref_name}}]'
-          pr-description: |
-            Updated Angular CLI help contents.
-          pr-labels: |
-            action: review
-            area: docs
-          angular-robot-token: ${{ secrets.ANGULAR_ROBOT_ACCESS_TOKEN }}

.gitignore

@@ -1,33 +1,21 @@
 .DS_STORE
 
 /dist/
-/bazel-out
-/integration/bazel/bazel-*
-*.log
-node_modules/
-
-# CircleCI temporary file for cache key computation.
-# See `save_month_to_file` in `.circleci/config.yml`.
-month.txt
+bazel-*
+e2e_test.*
+node_modules
+bower_components
+tools/gulp-tasks/cldr/cldr-data/
 
 # Include when developing application packages.
 pubspec.lock
 .c9
 .idea/
-.devcontainer/*
-!.devcontainer/README.md
-!.devcontainer/recommended-devcontainer.json
-!.devcontainer/recommended-Dockerfile
 .settings/
-.vscode/launch.json
-.vscode/settings.json
-.vscode/tasks.json
 *.swo
-*.swp
 modules/.settings
+.vscode
 modules/.vscode
-.vimrc
-.nvimrc
 
 # Don't check in secret files
 *secret.js
@@ -41,26 +29,3 @@ yarn-error.log
 
 # rollup-test output
 /modules/rollup-test/dist/
-
-# User specific bazel settings
-.bazelrc.user
-
-# User specific ng-dev settings
-.ng-dev.user*
-
-.notes.md
-baseline.json
-
-# Ignore .history for the xyz.local-history VSCode extension
-.history
-
-# Husky
-.husky/_
-
-
-# Ignore cache created with the Angular CLI.
-.angular/
-
-# Ignore AIO files, useful when changing branches
-aio/node_modules
-aio/out-tsc

.gitmessage

@@ -1,145 +0,0 @@
-<type>(<scope>): <summary>
-
-<Describe the motivation behind this change - explain WHY you are making this change. Wrap all lines
-at 100 characters.>
-
-Fixes #<issue number>
-
-# ────────────────────────────────────────── 100 chars ────────────────────────────────────────────┤
-
-
-# Example Commit Messages
-# =======================
-
-
-# ─── Example: Simple refactor ────────────────────────────────────────────────────────────────────┤
-# refactor(core): rename refreshDynamicEmbeddedViews to refreshEmbeddedViews
-#
-# Improve code readability. The original name no longer matches how the function is used.
-# ─────────────────────────────────────────────────────────────────────────────────────────────────┤
-
-
-# ─── Example: Simple docs change ─────────────────────────────────────────────────────────────────┤
-# docs: clarify the service limitation in providers.md guide
-#
-# Fixes #36332
-# ─────────────────────────────────────────────────────────────────────────────────────────────────┤
-
-
-# ─── Example: A bug fix ──────────────────────────────────────────────────────────────────────────┤
-# fix(ngcc): ensure lockfile is removed when `analyzeFn` fails
-#
-# Previously an error thrown in the `analyzeFn` would cause the ngcc process to exit immediately
-# without removing the lockfile, and potentially before the unlocker process had been successfully
-# spawned resulting in the lockfile being orphaned and left behind.
-#
-# Now we catch these errors and remove the lockfile as needed.
-# ─────────────────────────────────────────────────────────────────────────────────────────────────┤
-
-
-# ─── Example: Breaking change ────────────────────────────────────────────────────────────────────┤
-# feat(bazel): simplify ng_package by dropping esm5 and fesm5
-#
-# esm5 and fesm5 distributions are no longer needed and have been deprecated in the past.
-#
-# https://v9.angular.io/guide/deprecations#esm5-and-fesm5-code-formats-in-angular-npm-packages
-#
-# This commit modifies ng_package to no longer distribute these two formats in npm packages built by
-# ng_package (e.g. @angular/core).
-#
-# This commit intentionally doesn't fully clean up the ng_package rule to remove all traces of esm5
-# and fems5 build artifacts as that is a bigger cleanup and currently we are narrowing down the
-# scope of this change to the MVP needed for v10, which in this case is 'do not put esm5 and fesm5'
-# into the npm packages.
-#
-# More cleanup to follow: https://angular-team.atlassian.net/browse/FW-2143
-#
-# BREAKING CHANGE: esm5 and fesm5 format is no longer distributed in Angular's npm packages e.g.
-# @angular/core
-#
-# Angular CLI will automatically downlevel the code to es5 if differential loading is enabled in the
-# Angular project, so no action is required from Angular CLI users.
-#
-# If you are not using Angular CLI to build your application or library, and you need to be able to
-# build es5 artifacts, then you will need to downlevel the distributed Angular code to es5 on your
-# own.
-#
-#
-# Fixes #1234
-# ─────────────────────────────────────────────────────────────────────────────────────────────────┤
-
-
-
-# Angular Commit Message Format
-# =============================
-#
-# The full specification of the Angular Commit Message Format can be found at
-# https://github.com/angular/angular/blob/main/CONTRIBUTING.md#commit
-#
-# The following is an excerpt of the specification with the most commonly needed info.
-#
-# Each commit message consists of a *header*, a *body*, and a *footer*.
-#
-# <header>
-# <BLANK LINE>
-# <body>
-# <BLANK LINE>
-# <footer>
-#
-# The header is mandatory.
-#
-# The body is mandatory for all commits except for those of scope "docs". When the body is required
-# it must be at least 20 characters long.
-#
-# The footer is optional.
-#
-# Any line of the commit message cannot be longer than 100 characters.
-#
-#
-# Commit Message Header
-# ---------------------
-#
-# <type>(<scope>): <short summary>
-#   │       │             │
-#   │       │             └─⫸ Summary in present tense. Not capitalized. No period at the end.
-#   │       │
-#   │       └─⫸ Commit Scope: animations|bazel|benchpress|common|compiler|compiler-cli|core|
-#   │                          elements|forms|http|language-service|localize|platform-browser|
-#   │                          platform-browser-dynamic|platform-server|router|service-worker|
-#   │                          upgrade|zone.js|packaging|changelog|docs-infra|migrations|ngcc|ve|
-#   │                          devtools
-#   │                          https://github.com/angular/angular/blob/main/CONTRIBUTING.md#scope
-#   │
-#   └─⫸ Commit Type: build|ci|docs|feat|fix|perf|refactor|style|test
-#                     https://github.com/angular/angular/blob/main/CONTRIBUTING.md#type
-#
-#
-# Commit Message Body
-# ---------------------
-#
-# Just as in the summary, use the imperative, present tense: "fix" not "fixed" nor "fixes".
-#
-# Explain the motivation for the change in the commit message body. This commit message should
-# explain WHY you are making the change. You can include a comparison of the previous behavior with
-# the new behavior in order to illustrate the impact of the change.
-#
-#
-# Commit Message Footer
-# ---------------------
-#
-# The footer can contain information about breaking changes and is also the place to reference
-# GitHub issues, Jira tickets, and other PRs that this commit closes or is related to.
-#
-# ```
-# BREAKING CHANGE: <breaking change summary>
-# <BLANK LINE>
-# <breaking change description + migration instructions>
-# <BLANK LINE>
-# <BLANK LINE>
-# Fixes #<issue number>
-# ```
-#
-# Breaking Change section should start with the phrase "BREAKING CHANGE: " followed by a summary of
-# the breaking change, a blank line, and a detailed description of the breaking change that also
-# includes migration instructions.
-#

.husky/commit-msg

@@ -1,8 +0,0 @@
-set +e
-
-yarn -s ng-dev commit-message pre-commit-validate --file $1 2>/dev/null
-if [ $? -ne 0 ]; then
-  echo "WARNING: failed to run commit message validation (ng-dev commit-mesage pre-commit-validate)"
-fi
-
-exit 0;

.husky/pre-commit

@@ -1,8 +0,0 @@
-set +e
-
-yarn -s ng-dev format staged 2>/dev/null
-if [ $? -ne 0 ]; then
-  echo "WARNING: failed to run file formatting (ng-dev format staged)"
-fi
-
-exit 0;

.husky/prepare-commit-msg

@@ -1,8 +0,0 @@
-set +e
-
-yarn -s ng-dev commit-message restore-commit-message-draft $1 $2 2>/dev/null
-if [ $? -ne 0 ]; then
-  echo "WARNING: failed to attempt to restore commit message draft (ng-dev commit-message restore-commit-message-draft)"
-fi
-
-exit 0;

.ng-dev/caretaker.mts

@@ -1,21 +0,0 @@
-import {CaretakerConfig} from '@angular/ng-dev';
-
-/** The configuration for `ng-dev caretaker` commands. */
-export const caretaker: CaretakerConfig = {
-  g3SyncConfigPath: './.ng-dev/google-sync-config.json',
-  githubQueries: [
-    {
-      name: 'Merge Queue',
-      query: `is:pr is:open status:success label:"action: merge"`,
-    },
-    {
-      name: 'Merge Assistance Queue',
-      query: `is:pr is:open label:"merge: caretaker note" label:"action: merge"`,
-    },
-    {
-      name: 'Initial Triage Queue',
-      query: `is:open no:milestone -draft:true`,
-    },
-  ],
-  caretakerGroup: 'angular-caretaker',
-};

.ng-dev/commit-message.mts

@@ -1,38 +0,0 @@
-import {CommitMessageConfig} from '@angular/ng-dev';
-
-/**
- * The configuration for `ng-dev commit-message` commands.
- */
-export const commitMessage: CommitMessageConfig = {
-  maxLineLength: Infinity,
-  minBodyLength: 20,
-  minBodyLengthTypeExcludes: ['docs'],
-  scopes: [
-    'animations',
-    'bazel',
-    'benchpress',
-    'changelog',
-    'common',
-    'compiler',
-    'compiler-cli',
-    'core',
-    'dev-infra',
-    'devtools',
-    'docs-infra',
-    'elements',
-    'forms',
-    'http',
-    'language-service',
-    'localize',
-    'migrations',
-    'packaging',
-    'platform-browser',
-    'platform-browser-dynamic',
-    'platform-server',
-    'router',
-    'service-worker',
-    'upgrade',
-    've',
-    'zone.js',
-  ],
-};

.ng-dev/config.mts

@@ -1,15 +0,0 @@
-import {caretaker} from './caretaker.mjs';
-import {commitMessage} from './commit-message.mjs';
-import {format} from './format.mjs';
-import {github} from './github.mjs';
-import {pullRequest} from './pull-request.mjs';
-import {release} from './release.mjs';
-
-export {
-  commitMessage,
-  format,
-  github,
-  pullRequest,
-  caretaker,
-  release,
-};

.ng-dev/format.mts

@@ -1,31 +0,0 @@
-import {FormatConfig} from '@angular/ng-dev';
-
-/**
- * Configuration for the `ng-dev format` command.
- */
-export const format: FormatConfig = {
-  'prettier': {
-    'matchers': [
-      '**/*.{yaml,yml}',
-      '**/*.{js,ts}',
-
-      // Do not format d.ts files as they are generated
-      '!**/*.d.ts',
-      // Both third_party and .yarn are directories containing copied code which should
-      // not be modified.
-      '!third_party/**',
-      '!.yarn/**',
-      // Do not format the locale files which are checked-in for Google3, but generated using
-      // the `generate-locales-tool` from `packages/common/locales`.
-      '!packages/core/src/i18n/locale_en.ts',
-      '!packages/common/locales/closure-locale.ts',
-      '!packages/common/src/i18n/currencies.ts',
-      // Test cases contain non valid code.
-      '!packages/compiler-cli/test/compliance/test_cases/**/*.{js,ts}',
-
-      // Ignore generated javascript file(s)
-      '!.github/actions/deploy-docs-site/main.js',
-    ],
-  },
-  'buildifier': true,
-};

.ng-dev/gitconfig

@@ -1,15 +0,0 @@
-# The file is inert unless it's explicitly included into the local git config via:
-#
-# ```
-# git config --add include.path '../.ng-dev/gitconfig'
-# ```
-#
-# Calling that command will append the following into `.git/config` of the current git workspace
-# (i.e. $GIT_DIR, typically `angular/.git/config`):
-#
-# ```
-# [include]
-#     path = ../.ng-dev/gitconfig
-# ```
-[commit]
-  template = .gitmessage

.ng-dev/github.mts

@@ -1,12 +0,0 @@
-import {GithubConfig} from '@angular/ng-dev';
-
-/**
- * Github configuration for the `ng-dev` command. This repository is used as
- * remote for the merge script and other utilities like `ng-dev pr rebase`.
- */
-export const github: GithubConfig = {
-  owner: 'angular',
-  name: 'angular',
-  mainBranchName: 'main',
-  useNgDevAuthService: true,
-};

.ng-dev/google-sync-config.json

@@ -1,55 +0,0 @@
-{
-  "syncedFilePatterns": [
-    "LICENSE",
-    "modules/benchmarks/**",
-    "packages/**"
-  ],
-  "separateFilePatterns": [
-    "packages/core/primitives/**"
-  ],
-  "alwaysExternalFilePatterns": [
-    "packages/*",
-    "packages/bazel/*",
-    "packages/bazel/src/*",
-    "packages/bazel/src/api-extractor/**",
-    "packages/bazel/src/builders/**",
-    "packages/bazel/src/ng_module/**",
-    "packages/bazel/src/ng_package/**",
-    "packages/bazel/src/protractor/**",
-    "packages/bazel/src/schematics/**",
-    "packages/bazel/src/types_bundle/**",
-    "packages/compiler-cli/linker/**",
-    "packages/compiler-cli/src/ngtsc/sourcemaps/**",
-    "packages/compiler-cli/src/ngtsc/testing/**",
-    "packages/compiler-cli/private/bazel.ts",
-    "packages/compiler-cli/private/localize.ts",
-    "packages/compiler-cli/private/tooling.ts",
-    "packages/compiler-cli/private/babel.d.ts",
-    "packages/compiler-cli/src/bin/**",
-    "packages/docs/**",
-    "packages/elements/schematics/**",
-    "packages/examples/**",
-    "packages/localize/**",
-    "packages/private/**",
-    "packages/service-worker/**",
-    "packages/common/locales/generate-locales-tool/**",
-    "packages/common/locales/index.bzl",
-    "packages/http/**",
-    "**/.gitignore",
-    "**/.gitkeep",
-    "**/third_party/**",
-    "**/tsconfig-build.json",
-    "**/tsconfig-tsec.json",
-    "**/tsconfig.json",
-    "**/rollup.config.js",
-    "**/BUILD.bazel",
-    "**/*.md",
-    "packages/**/integrationtest/**",
-    "packages/**/test/**",
-    "packages/zone.js/*",
-    "packages/zone.js/dist/**",
-    "packages/zone.js/doc/**",
-    "packages/zone.js/example/**",
-    "packages/zone.js/scripts/**"
-  ]
-}

.ng-dev/pull-request.mts

@@ -1,25 +0,0 @@
-import {PullRequestConfig} from '@angular/ng-dev';
-
-/**
- * Configuration for the merge tool in `ng-dev`. This sets up the labels which
- * are respected by the merge script (e.g. the target labels).
- */
-export const pullRequest: PullRequestConfig = {
-  githubApiMerge: false,
-  requiredBaseCommits: {
-    // PRs that target either `main` or the patch branch, need to be rebased
-    // on top of the latest commit message validation fix.
-    // These SHAs are the commits that update the required license text in the header.
-    'main': '5aeb9a4124922d8ac08eb73b8f322905a32b0b3a',
-    '10.0.x': '27b95ba64a5d99757f4042073fd1860e20e3ed24',
-  },
-  // `dev-infra` and `docs-infra` are not affecting the public NPM packages. Similarly,
-  // the `bazel` package is not considered part of the public API so that features
-  // can land in patch branches.
-  targetLabelExemptScopes: ['dev-infra', 'docs-infra', 'bazel'],
-  // enables specific validations during the pull request merge process
-  validators: {
-    assertEnforceTested: true,
-    assertIsolatedSeparateFiles: true,
-  },
-};

.ng-dev/release.mts

@@ -1,34 +0,0 @@
-import {ReleaseConfig} from '@angular/ng-dev';
-
-/** Configuration for the `ng-dev release` command. */
-export const release: ReleaseConfig = {
-  publishRegistry: 'https://wombat-dressing-room.appspot.com',
-  representativeNpmPackage: '@angular/core',
-  npmPackages: [
-    {name: '@angular/animations'},
-    {name: '@angular/common'},
-    {name: '@angular/compiler'},
-    {name: '@angular/compiler-cli'},
-    {name: '@angular/core'},
-    {name: '@angular/elements'},
-    {name: '@angular/forms'},
-    {name: '@angular/language-service'},
-    {name: '@angular/localize'},
-    {name: '@angular/platform-browser'},
-    {name: '@angular/platform-browser-dynamic'},
-    {name: '@angular/platform-server'},
-    {name: '@angular/router'},
-    {name: '@angular/service-worker'},
-    {name: '@angular/upgrade'},
-  ],
-  buildPackages: async () => {
-    // The buildTargetPackages function is loaded at runtime as the loading the script
-    // causes an invocation of Bazel.
-    const {performNpmReleaseBuild} = await import('../scripts/build/package-builder.mjs');
-    return performNpmReleaseBuild();
-  },
-  releaseNotes: {
-    hiddenScopes: ['bazel', 'dev-infra', 'docs-infra', 'zone.js', 'devtools'],
-  },
-  releasePrLabels: ['area: build & ci', 'action: merge', 'PullApprove: disable'],
-};

.ng-dev/tsconfig.json

@@ -1,10 +0,0 @@
-{
-  "compilerOptions": {
-    "strict": true,
-    "target": "es2020",
-    "module": "Node16",
-    "noEmit": true,
-    "skipLibCheck": true,
-    "types": []
-  }
-}

.npmrc

@@ -1 +0,0 @@
-engine-strict = true

.nvmrc

@@ -1 +1 @@
-18.20.0
+10.9.0

.prettierrc

@@ -1,10 +0,0 @@
-{
-  "printWidth": 100,
-  "tabWidth": 2,
-  "useTabs": false,
-  "embeddedLanguageFormatting": "off",
-  "singleQuote": true,
-  "semi": true,
-  "quoteProps": "preserve",
-  "bracketSpacing": false
-}

.travis.yml

@@ -0,0 +1,76 @@
+language: node_js
+sudo: false
+dist: trusty
+node_js:
+  - '10.9.0'
+
+addons:
+#  firefox: "38.0"
+  apt:
+    sources:
+      # needed to install g++ that is used by npms's native modules
+      - ubuntu-toolchain-r-test
+    packages:
+      # needed to install g++ that is used by npms's native modules
+      - g++-4.8
+
+branches:
+  except:
+    - g3
+
+cache:
+  yarn: true
+  directories:
+     - ./node_modules
+     - ./.chrome/chromium
+     - ./aio/node_modules
+
+env:
+  global:
+    # GITHUB_TOKEN_ANGULAR=<github token, a personal access token of the angular-builds account, account access in valentine>
+    # This is needed for the e2e Travis matrix task to publish packages to github for continuous packages delivery.
+    - secure: "aCdHveZuY8AT4Jr1JoJB4LxZsnGWRe/KseZh1YXYe5UtufFCtTVHvUcLn0j2aLBF0KpdyS+hWf0i4np9jthKu2xPKriefoPgCMpisYeC0MFkwbmv+XlgkUbgkgVZMGiVyX7DCYXVahxIoOUjVMEDCbNiHTIrfEuyq24U3ok2tHc="
+    # FIREBASE_TOKEN
+    # This is needed for publishing builds to the "aio-staging" and "angular-io" firebase projects.
+    # This token was generated using the aio-deploy@angular.io account using `firebase login:ci` and password from valentine
+    - secure: "L5CyQmpwWtoR4Qi4xlWQh/cL1M6ZeJL4W4QAr4HdKFMgYt9h+Whqkymyh2NxwmCbPvWa7yUd+OiLQUDCY7L2VIg16hTwoe2CgYDyQA0BEwLzxtRrJXl93TfwMlrUx5JSIzAccD6D4sjtz8kSFMomK2Nls33xOXOukwyhVMjd0Cg="
+    # ANGULAR_PAYLOAD_FIREBASE_TOKEN
+    # This is for payload size data to "angular-payload-size" firebase project
+    # This token was generated using the payload@angular.io account using `firebase login:ci` and password from valentine
+    - secure: "SxotP/ymNy6uWAVbfwM9BlwETPEBpkRvU/F7fCtQDDic99WfQHzzUSQqHTk8eKk3GrGAOSL09vT0WfStQYEIGEoS5UHWNgOnelxhw+d5EnaoB8vQ0dKQBTK092hQg4feFprr+B/tCasyMV6mVwpUzZMbIJNn/Rx7H5g1bp+Gkfg="
+  matrix:
+    # Order: a slower build first, so that we don't occupy an idle travis worker waiting for others to complete.
+    - CI_MODE=e2e
+    - CI_MODE=js
+    - CI_MODE=saucelabs_required
+    # deactivated, see #19768
+    # - CI_MODE=browserstack_required
+    - CI_MODE=saucelabs_optional
+    - CI_MODE=browserstack_optional
+    - CI_MODE=aio_tools_test
+    - CI_MODE=aio
+    - CI_MODE=aio_e2e AIO_SHARD=0
+    - CI_MODE=aio_e2e AIO_SHARD=1
+
+matrix:
+  fast_finish: true
+  allow_failures:
+    - env: "CI_MODE=saucelabs_optional"
+    - env: "CI_MODE=browserstack_optional"
+
+before_install:
+  # source the env.sh script so that the exported variables are available to other scripts later on
+  - source ./scripts/ci/env.sh print
+
+install:
+  - ./scripts/ci/install.sh
+
+script:
+  - ./scripts/ci/build.sh
+  - ./scripts/ci/test.sh
+  # deploy is part of 'script' and not 'after_success' so that we fail the build if the deployment fails
+  - ./scripts/ci/deploy.sh
+  - ./scripts/ci/angular.sh
+  # all the scripts under this line will not quickly abort in case ${TRAVIS_TEST_RESULT} is 1 (job failure)
+  - ./scripts/ci/cleanup.sh
+  - ./scripts/ci/print-logs.sh

.vscode/README.md

@@ -1,25 +0,0 @@
-# VSCode Configuration
-
-This folder contains opt-in [Workspace Settings](https://code.visualstudio.com/docs/getstarted/settings), [Tasks](https://code.visualstudio.com/docs/editor/tasks), [Launch Configurations](https://code.visualstudio.com/Docs/editor/debugging#_launch-configurations) and [Extension Recommendations](https://code.visualstudio.com/docs/editor/extension-gallery#_workspace-recommended-extensions) that the Angular team recommends using when working on this repository.
-
-## Usage
-
-To use the recommended configurations follow the steps below:
-
-- install the recommended extensions in `.vscode/extensions.json`
-- copy (or link) `.vscode/recommended-settings.json` to `.vscode/settings.json`
-- copy (or link) `.vscode/recommended-launch.json` to `.vscode/launch.json`
-- copy (or link) `.vscode/recommended-tasks.json` to `.vscode/tasks.json`
-- restart the editor
-
-If you already have your custom workspace settings, you should instead manually merge the file contents.
-
-This isn't an automatic process, so you will need to repeat it when settings are updated.
-
-To see the recommended extensions select "Extensions: Show Recommended Extensions" in the [Command Palette](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette).
-
-## Editing `.vscode/recommended-*.json` files
-
-If you wish to add extra configuration items please keep in mind any modifications you make here will be used by many users.
-
-Try to keep these settings/configurations to things that help facilitate the development process and avoid altering the user workflow whenever possible.

.vscode/extensions.json

@@ -1,10 +0,0 @@
-{
-  // See https://go.microsoft.com/fwlink/?LinkId=827846 to learn about workspace recommendations.
-  // Extension identifier format: ${publisher}.${name}. Example: vscode.csharp
-
-  // List of extensions which should be recommended for users of this workspace.
-  "recommendations": [
-    "BazelBuild.vscode-bazel",
-    "ms-vscode.vscode-typescript-tslint-plugin",
-  ],
-}

.vscode/recommended-launch.json

@@ -1,75 +0,0 @@
-{
-  // Use IntelliSense to learn about possible attributes.
-  // Hover to view descriptions of existing attributes.
-  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
-  "version": "0.2.0",
-  "configurations": [
-    {
-      "name": "Attach to bazel test ... --config=debug",
-      "type": "node",
-      "request": "attach",
-      "port": 9229,
-      "address": "localhost",
-      "restart": false,
-      "sourceMaps": true,
-      "localRoot": "${workspaceRoot}",
-      "remoteRoot": "${workspaceRoot}",
-      "stopOnEntry": false,
-      "timeout": 600000,
-      "outFiles": ["${workspaceFolder}/dist/out/**/packages/**/*.js"]
-    },
-    {
-      "name": "Attach to bazel test ... --config=debug (no source maps)",
-      "type": "node",
-      "request": "attach",
-      "port": 9229,
-      "address": "localhost",
-      "restart": false,
-      "sourceMaps": false,
-      "localRoot": "${workspaceRoot}",
-      "remoteRoot": "${workspaceRoot}",
-      "stopOnEntry": false,
-      "timeout": 600000,
-      "outFiles": ["${workspaceFolder}/dist/out/**/packages/**/*.js"]
-    },
-    {
-      "name": "IVY:packages/core/test/acceptance",
-      "type": "node",
-      "request": "launch",
-      "program": "${workspaceFolder}/node_modules/.bin/bazelisk",
-      "args": ["test", "packages/core/test/acceptance", "--config=debug"],
-      "port": 9229,
-      "address": "localhost",
-      "restart": true,
-      "sourceMaps": true,
-      "timeout": 600000,
-      "outFiles": ["${workspaceFolder}/dist/out/**/packages/**/*.js"]
-    },
-    {
-      "name": "IVY:packages/core/test/render3",
-      "type": "node",
-      "request": "launch",
-      "program": "${workspaceFolder}/node_modules/.bin/bazelisk",
-      "args": ["test", "packages/core/test/render3", "--config=debug"],
-      "port": 9229,
-      "address": "localhost",
-      "restart": true,
-      "sourceMaps": true,
-      "timeout": 600000,
-      "outFiles": ["${workspaceFolder}/dist/out/**/packages/**/*.js"]
-    },
-    {
-      "name": "IVY:packages/core/test",
-      "type": "node",
-      "request": "launch",
-      "program": "${workspaceFolder}/node_modules/.bin/bazelisk",
-      "args": ["test", "packages/core/test", "--config=debug"],
-      "port": 9229,
-      "address": "localhost",
-      "restart": true,
-      "sourceMaps": true,
-      "timeout": 600000,
-      "outFiles": ["${workspaceFolder}/dist/out/**/packages/**/*.js"]
-    }
-  ]
-}

.vscode/recommended-settings.json

@@ -1,24 +0,0 @@
-{
-  "[javascript]": {
-    "editor.formatOnSave": true,
-  },
-  "[typescript]": {
-    "editor.formatOnSave": true,
-  },
-  // Exclude third party modules and build artifacts from the editor watchers/searches.
-  "files.watcherExclude": {
-    "**/.git/objects/**": true,
-    "**/.git/subtree-cache/**": true,
-    "**/node_modules/**": true,
-    "**/bazel-out/**": true,
-    "**/dist/**": true,
-  },
-  "search.exclude": {
-    "**/node_modules": true,
-    "**/bower_components": true,
-    "**/bazel-out": true,
-    "**/dist": true,
-    ".history": true,
-  },
-  "git.ignoreLimitWarning": true,
-}

.vscode/recommended-tasks.json

@@ -1,109 +0,0 @@
-{
-  // See https://go.microsoft.com/fwlink/?LinkId=733558
-  // for the documentation about the tasks.json format
-  "version": "2.0.0",
-  "tasks": [
-    {
-      "label": "IVY:packages/core/test/...",
-      "type": "shell",
-      "command": "${workspaceFolder}/node_modules/.bin/bazelisk",
-      "args": [
-        "test",
-        "packages/core/test",
-        "packages/core/test/acceptance",
-        "packages/core/test/render3",
-      ],
-      "group": "test",
-      "presentation": {
-        "reveal": "always",
-        "panel": "dedicated",
-      },
-    },
-    {
-      "label": "VE:packages/core/test/...",
-      "type": "shell",
-      "command": "${workspaceFolder}/node_modules/.bin/bazelisk",
-      "args": [
-        "test",
-        "packages/core/test",
-        "packages/core/test/acceptance",
-        "packages/core/test/render3",
-      ],
-      "group": "test",
-      "presentation": {
-        "reveal": "always",
-        "panel": "dedicated",
-      },
-    },
-    {
-      "label": "IVY:packages/core/test/acceptance",
-      "type": "shell",
-      "command": "${workspaceFolder}/node_modules/.bin/bazelisk",
-      "args": [
-        "test",
-        "packages/core/test/acceptance",
-      ],
-      "group": "test",
-      "presentation": {
-        "reveal": "always",
-        "panel": "dedicated",
-      },
-    },
-    {
-      "label": "VE:packages/core/test/acceptance",
-      "type": "shell",
-      "command": "${workspaceFolder}/node_modules/.bin/bazelisk",
-      "args": [
-        "test",
-        "packages/core/test/acceptance",
-      ],
-      "group": "test",
-      "presentation": {
-        "reveal": "always",
-        "panel": "dedicated",
-      },
-    },
-    {
-      "label": "IVY:packages/core/test",
-      "type": "shell",
-      "command": "${workspaceFolder}/node_modules/.bin/bazelisk",
-      "args": [
-        "test",
-        "packages/core/test",
-      ],
-      "group": "test",
-      "presentation": {
-        "reveal": "always",
-        "panel": "dedicated",
-      },
-    },
-    {
-      "label": "VE:packages/core/test",
-      "type": "shell",
-      "command": "${workspaceFolder}/node_modules/.bin/bazelisk",
-      "args": [
-        "test",
-        "packages/core/test",
-      ],
-      "group": "test",
-      "presentation": {
-        "reveal": "always",
-        "panel": "dedicated",
-      },
-    },
-    {
-      "label": "IVY:packages/core/test/render3",
-      "type": "shell",
-      "command": "${workspaceFolder}/node_modules/.bin/bazelisk",
-      "args": [
-        "test",
-        "packages/core/test/render3",
-      ],
-      "group": "test",
-      "presentation": {
-        "reveal": "always",
-        "panel": "dedicated",
-      },
-    },
-  ],
-}

.yarn/README.md

@@ -1,13 +0,0 @@
-# Yarn Vendoring
-We utilize Yarn's `yarn-path` configuration in a shared `.yarnrc` file to enforce
-everyone using the same version of Yarn.  Yarn checks the `.yarnrc` file to
-determine if yarn should delegate the command to a vendored version at the
-provided path.
-
-## How to update
-To update to the latest version of Yarn as our vendored version:
-- Run this command
-```sh
-yarn policies set-version latest
-```
-- Remove the previous version

.yarnrc

@@ -1,5 +0,0 @@
-# THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY.
-# yarn lockfile v1
-
-
-yarn-path ".yarn/releases/yarn-1.22.22.cjs"

BUILD.bazel

@@ -1,81 +1,57 @@
-load("//tools:defaults.bzl", "nodejs_binary")
-load("@build_bazel_rules_nodejs//:index.bzl", "js_library")
-load("//:yarn.bzl", "YARN_PATH")
-
 package(default_visibility = ["//visibility:public"])
 
+load("@build_bazel_rules_nodejs//:defs.bzl", "node_modules_filegroup")
+
 exports_files([
+    "tsconfig.json",
     "LICENSE",
-    "karma-js.conf.js",
-    "browser-providers.conf.js",
-    YARN_PATH,
-    "scripts/ci/bazel-payload-size.sh",
-    "scripts/ci/payload-size.sh",
-    "scripts/ci/payload-size.js",
-    "package.json",
-    "angular.json",
+    "protractor-perf.conf.js",
 ])
 
-filegroup(
-    # filegroup is needed so that this package.json file can be a dep
-    # in a js_library target, which doesn't allow source file deps
-    name = "package_json",
-    srcs = ["package.json"],
-)
-
+# Developers should always run `bazel run :install`
+# This ensures that package.json in subdirectories get installed as well.
 alias(
-    name = "tsconfig.json",
-    actual = "//packages:tsconfig-build.json",
+    name = "install",
+    actual = "@nodejs//:yarn",
 )
 
-js_library(
-    name = "browser-providers",
+filegroup(
+    name = "web_test_bootstrap_scripts",
+    # do not sort
     srcs = [
-        "browser-providers.conf.d.ts",
-        "browser-providers.conf.js",
+        "@ngdeps//node_modules/reflect-metadata:Reflect.js",
+        "@ngdeps//node_modules/zone.js:dist/zone.js",
+        "@ngdeps//node_modules/zone.js:dist/zone-testing.js",
+        "@ngdeps//node_modules/zone.js:dist/task-tracking.js",
+        "//:test-events.js",
     ],
 )
 
 filegroup(
     name = "angularjs_scripts",
     srcs = [
-        # We also declare the unminified AngularJS files since these can be used for
-        # local debugging (e.g. see: packages/upgrade/test/common/test_helpers.ts)
-        "@npm//:node_modules/angular-1.5/angular.js",
-        "@npm//:node_modules/angular-1.5/angular.min.js",
-        "@npm//:node_modules/angular-1.6/angular.js",
-        "@npm//:node_modules/angular-1.6/angular.min.js",
-        "@npm//:node_modules/angular-1.7/angular.js",
-        "@npm//:node_modules/angular-1.7/angular.min.js",
-        "@npm//:node_modules/angular-mocks-1.5/angular-mocks.js",
-        "@npm//:node_modules/angular-mocks-1.6/angular-mocks.js",
-        "@npm//:node_modules/angular-mocks-1.7/angular-mocks.js",
-        "@npm//:node_modules/angular-mocks-1.8/angular-mocks.js",
-        "@npm//:node_modules/angular-1.8/angular.js",
-        "@npm//:node_modules/angular-1.8/angular.min.js",
+        "@ngdeps//node_modules/angular:angular.js",
+        "@ngdeps//node_modules/angular-1.5:angular.js",
+        "@ngdeps//node_modules/angular-1.6:angular.js",
+        "@ngdeps//node_modules/angular-mocks:angular-mocks.js",
+        "@ngdeps//node_modules/angular-mocks-1.5:angular-mocks.js",
+        "@ngdeps//node_modules/angular-mocks-1.6:angular-mocks.js",
     ],
 )
 
-# Detect if the build is running under --stamp
-config_setting(
-    name = "stamp",
-    values = {"stamp": "true"},
-)
+load("@build_bazel_rules_nodejs//:defs.bzl", "nodejs_binary")
 
+# A nodejs_binary for @angular/bazel/ngc-wrapped to use by default in
+# ng_module that depends on @npm//@angular/bazel instead of the
+# output of the //packages/bazel/src/ngc-wrapped ts_library rule. This
+# default is for downstream users that depend on the @angular/bazel npm
+# package. The generated @npm//@angular/bazel/ngc-wrapped target
+# does not work because it does not have the node `--expose-gc` flag
+# set which is required to support the call to `global.gc()`.
 nodejs_binary(
-    name = "yarn_vendored",
-    data = [".yarn/releases/yarn-1.22.22.cjs"],
-    entry_point = ".yarn/releases/yarn-1.22.22.cjs",
-    visibility = [
-        "//integration:__subpackages__",
-    ],
-)
-
-alias(
-    name = "sauce_connect",
-    actual = select({
-        "@npm//@angular/build-tooling/bazel/constraints:linux_x64": "@sauce_connect_linux_amd64//:bin/sc",
-        "@npm//@angular/build-tooling/bazel/constraints:macos_x64": "@sauce_connect_mac//:bin/sc",
-        "@npm//@angular/build-tooling/bazel/constraints:macos_arm64": "@sauce_connect_mac//:bin/sc",
-    }),
+    name = "@angular/bazel/ngc-wrapped",
+    data = ["@npm//@angular/bazel"],
+    entry_point = "@angular/bazel/src/ngc-wrapped/index.js",
+    install_source_map_support = False,
+    templated_args = ["--node_options=--expose-gc"],
 )

CODE_OF_CONDUCT.md

@@ -1,79 +1,12 @@
-# Contributor Covenant Code of Conduct
+# Contributor Code of Conduct
+## Version 0.3b-angular
 
-## Our Pledge
+As contributors and maintainers of the Angular project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities.
 
-In the interest of fostering a safe and welcoming environment, we as
-the Angular team pledge to make participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity, gender expression,
-level of experience, education, socio-economic status, nationality, personal
-appearance, race, religion, or sexual identity and orientation.
+Communication through any of Angular's channels (GitHub, Gitter, IRC, mailing lists, Google+, Twitter, etc.) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.
 
-## Our Standards
+We promise to extend courtesy and respect to everyone involved in this project regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to the Angular project to do the same.
 
-Examples of behavior that contributes to creating a positive environment
-include:
+If any member of the community violates this code of conduct, the maintainers of the Angular project may take action, removing issues, comments, and PRs or blocking accounts as deemed appropriate.
 
-* Use welcoming and inclusive language
-* Respect each other
-* Provide and gracefully accept constructive criticism
-* Show empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* The use of sexualized language or imagery
-* Unwelcome sexual attention or advances
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Angular team are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Angular team have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, and to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies to all Angular communication channels - online or in person,
-and it also applies when an individual is representing the project or its community in
-public spaces. Examples of representing a project or community include using an official
-project e-mail address, posting via an official social media account, or acting
-as an appointed representative at an online or offline event. Representation of
-a project may be further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the Angular team at conduct@angular.io. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The Angular team
-will maintain confidentiality with regard to the reporter of an incident.
-Enforcement may result in an indefinite ban from all official Angular communication
-channels, or other actions as deemed appropriate by the Angular team.
-
-Angular maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-### Appeal
-
-If you are banned you may contest the decision. To do so email conduct@angular.io with the subject line "Repeal Ban for {{your name here}}" and body with the responses to the following:
-
-* Why do you believe you did not violate the Code of Conduct?
-* Were other factors involved in this situation the leadership team may have been unaware of?
-* Why do you wish to be a part of the Angular community?
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+If you are subject to or witness unacceptable behavior, or have any other concerns, please email us at [conduct@angular.io](mailto:conduct@angular.io).

CONTRIBUTING.md

@@ -1,7 +1,7 @@
 # Contributing to Angular
 
-We would love for you to contribute to Angular and help make it even better than it is today!
-As a contributor, here are the guidelines we would like you to follow:
+We would love for you to contribute to Angular and help make it even better than it is
+today! As a contributor, here are the guidelines we would like you to follow:
 
  - [Code of Conduct](#coc)
  - [Question or Problem?](#question)
@@ -12,168 +12,110 @@ As a contributor, here are the guidelines we would like you to follow:
  - [Commit Message Guidelines](#commit)
  - [Signing the CLA](#cla)
 
-
 ## <a name="coc"></a> Code of Conduct
-
-Help us keep Angular open and inclusive.
-Please read and follow our [Code of Conduct][coc].
-
+Help us keep Angular open and inclusive. Please read and follow our [Code of Conduct][coc].
 
 ## <a name="question"></a> Got a Question or Problem?
 
-Do not open issues for general support questions as we want to keep GitHub issues for bug reports and feature requests.
-Instead, we recommend using [Stack Overflow](https://stackoverflow.com/questions/tagged/angular) to ask support-related questions. When creating a new question on Stack Overflow, make sure to add the `angular` tag.
+Do not open issues for general support questions as we want to keep GitHub issues for bug reports and feature requests. You've got much better chances of getting your question answered on [Stack Overflow](https://stackoverflow.com/questions/tagged/angular) where the questions should be tagged with tag `angular`.
 
 Stack Overflow is a much better place to ask questions since:
 
 - there are thousands of people willing to help on Stack Overflow
-- questions and answers stay available for public viewing so your question/answer might help someone else
+- questions and answers stay available for public viewing so your question / answer might help someone else
 - Stack Overflow's voting system assures that the best answers are prominently visible.
 
 To save your and our time, we will systematically close all issues that are requests for general support and redirect people to Stack Overflow.
 
-If you would like to chat about the question in real-time, you can reach out via [the Angular community Discord server][discord].
-
+If you would like to chat about the question in real-time, you can reach out via [our gitter channel][gitter].
 
 ## <a name="issue"></a> Found a Bug?
-
-If you find a bug in the source code, you can help us by [submitting an issue](#submit-issue) to our [GitHub Repository][github].
-Even better, you can [submit a Pull Request](#submit-pr) with a fix.
-
+If you find a bug in the source code, you can help us by
+[submitting an issue](#submit-issue) to our [GitHub Repository][github]. Even better, you can
+[submit a Pull Request](#submit-pr) with a fix.
 
 ## <a name="feature"></a> Missing a Feature?
-You can *request* a new feature by [submitting an issue](#submit-issue) to our GitHub Repository.
-If you would like to *implement* a new feature, please consider the size of the change in order to determine the right steps to proceed:
-
-* For a **Major Feature**, first open an issue and outline your proposal so that it can be discussed.
-  This process allows us to better coordinate our efforts, prevent duplication of work, and help you to craft the change so that it is successfully accepted into the project.
-
-  **Note**: Adding a new topic to the documentation, or significantly re-writing a topic, counts as a major feature.
+You can *request* a new feature by [submitting an issue](#submit-issue) to our GitHub
+Repository. If you would like to *implement* a new feature, please submit an issue with
+a proposal for your work first, to be sure that we can use it.
+Please consider what kind of change it is:
 
+* For a **Major Feature**, first open an issue and outline your proposal so that it can be
+discussed. This will also allow us to better coordinate our efforts, prevent duplication of work,
+and help you to craft the change so that it is successfully accepted into the project.
 * **Small Features** can be crafted and directly [submitted as a Pull Request](#submit-pr).
 
-
 ## <a name="submit"></a> Submission Guidelines
 
-
 ### <a name="submit-issue"></a> Submitting an Issue
 
-Before you submit an issue, please search the issue tracker. An issue for your problem might already exist and the discussion might inform you of workarounds readily available.
+Before you submit an issue, please search the issue tracker, maybe an issue for your problem already exists and the discussion might inform you of workarounds readily available.
 
-We want to fix all the issues as soon as possible, but before fixing a bug, we need to reproduce and confirm it.
-In order to reproduce bugs, we require that you provide a minimal reproduction.
-Having a minimal reproducible scenario gives us a wealth of important information without going back and forth to you with additional questions.
+We want to fix all the issues as soon as possible, but before fixing a bug we need to reproduce and confirm it. In order to reproduce bugs, we will systematically ask you to provide a minimal reproduction scenario using http://plnkr.co. Having a live, reproducible scenario gives us a wealth of important information without going back & forth to you with additional questions like:
 
-A minimal reproduction allows us to quickly confirm a bug (or point out a coding problem) as well as confirm that we are fixing the right problem.
+- version of Angular used
+- 3rd-party libraries and their versions
+- and most importantly - a use-case that fails
 
-We require a minimal reproduction to save maintainers' time and ultimately be able to fix more bugs.
-Often, developers find coding problems themselves while preparing a minimal reproduction.
-We understand that sometimes it might be hard to extract essential bits of code from a larger codebase, but we really need to isolate the problem before we can fix it.
+A minimal reproduce scenario using http://plnkr.co/ allows us to quickly confirm a bug (or point out coding problem) as well as confirm that we are fixing the right problem. If plunker is not a suitable way to demonstrate the problem (for example for issues related to our npm packaging), please create a standalone git repository demonstrating the problem.
 
-Unfortunately, we are not able to investigate / fix bugs without a minimal reproduction, so if we don't hear back from you, we are going to close an issue that doesn't have enough info to be reproduced.
+We will be insisting on a minimal reproduce scenario in order to save maintainers time and ultimately be able to fix more bugs. Interestingly, from our experience users often find coding problems themselves while preparing a minimal plunk. We understand that sometimes it might be hard to extract essentials bits of code from a larger code-base but we really need to isolate the problem before we can fix it.
 
-You can file new issues by selecting from our [new issue templates](https://github.com/angular/angular/issues/new/choose) and filling out the issue template.
+Unfortunately, we are not able to investigate / fix bugs without a minimal reproduction, so if we don't hear back from you we are going to close an issue that doesn't have enough info to be reproduced.
+
+You can file new issues by filling out our [new issue form](https://github.com/angular/angular/issues/new).
 
 
 ### <a name="submit-pr"></a> Submitting a Pull Request (PR)
-
 Before you submit your Pull Request (PR) consider the following guidelines:
 
-1. Search [GitHub](https://github.com/angular/angular/pulls) for an open or closed PR that relates to your submission.
-   You don't want to duplicate existing efforts.
-
-2. Be sure that an issue describes the problem you're fixing, or documents the design for the feature you'd like to add.
-   Discussing the design upfront helps to ensure that we're ready to accept your work.
-
-3. Please sign our [Contributor License Agreement (CLA)](#cla) before sending PRs.
-   We cannot accept code without a signed CLA.
-   Make sure you author all contributed Git commits with email address associated with your CLA signature.
-
-4. [Fork](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo) the [angular/angular](https://github.com/angular/angular/fork) repo.
-
-5. In your forked repository, make your changes in a new git branch:
+1. Search [GitHub](https://github.com/angular/angular/pulls) for an open or closed PR
+  that relates to your submission. You don't want to duplicate effort.
+1. Please sign our [Contributor License Agreement (CLA)](#cla) before sending PRs.
+  We cannot accept code without this. Make sure you sign with the primary email address of the Git identity that has been granted access to the Angular repository.
+1. Fork the angular/angular repo.
+1. Make your changes in a new git branch:
 
      ```shell
-     git checkout -b my-fix-branch main
+     git checkout -b my-fix-branch master
      ```
 
-6. Create your patch, **including appropriate test cases**.
-
-7. Follow our [Coding Rules](#rules).
-
-8. Run the full Angular test suite, as described in the [developer documentation][dev-doc], and ensure that all tests pass.
-
-9. Commit your changes using a descriptive commit message that follows our [commit message conventions](#commit).
-   Adherence to these conventions is necessary because release notes are automatically generated from these messages.
+1. Create your patch, **including appropriate test cases**.
+1. Follow our [Coding Rules](#rules).
+1. Run the full Angular test suite, as described in the [developer documentation][dev-doc],
+  and ensure that all tests pass.
+1. Commit your changes using a descriptive commit message that follows our
+  [commit message conventions](#commit). Adherence to these conventions
+  is necessary because release notes are automatically generated from these messages.
 
      ```shell
-     git commit --all
+     git commit -a
      ```
-    Note: the optional commit `--all` command line option will automatically "add" and "rm" edited files.
+    Note: the optional commit `-a` command line option will automatically "add" and "rm" edited files.
 
-10. Push your branch to GitHub:
+1. Push your branch to GitHub:
 
     ```shell
     git push origin my-fix-branch
     ```
 
-11. In GitHub, send a pull request to `angular:main`.
-
-### Reviewing a Pull Request
-
-The Angular team reserves the right not to accept pull requests from community members who haven't been good citizens of the community. Such behavior includes not following the [Angular code of conduct](https://github.com/angular/code-of-conduct) and applies within or outside of Angular managed channels.
-
-#### Addressing review feedback
-
-If we ask for changes via code reviews then:
-
-1. Make the required updates to the code.
-
-2. Re-run the Angular test suites to ensure tests are still passing.
-
-3. Create a fixup commit and push to your GitHub repository (this will update your Pull Request):
+1. In GitHub, send a pull request to `angular:master`.
+* If we suggest changes then:
+  * Make the required updates.
+  * Re-run the Angular test suites to ensure tests are still passing.
+  * Rebase your branch and force push to your GitHub repository (this will update your Pull Request):
 
     ```shell
-    git commit --all --fixup HEAD
-    git push
+    git rebase master -i
+    git push -f
     ```
 
-    For more info on working with fixup commits see [here](./contributing-docs/using-fixup-commits.md).
-
 That's it! Thank you for your contribution!
 
-
-##### Updating the commit message
-
-A reviewer might often suggest changes to a commit message (for example, to add more context for a change or adhere to our [commit message guidelines](#commit)).
-In order to update the commit message of the last commit on your branch:
-
-1. Check out your branch:
-
-    ```shell
-    git checkout my-fix-branch
-    ```
-
-2. Amend the last commit and modify the commit message:
-
-    ```shell
-    git commit --amend
-    ```
-
-3. Push to your GitHub repository:
-
-    ```shell
-    git push --force-with-lease
-    ```
-
-> NOTE:<br />
-> If you need to update the commit message of an earlier commit, you can use `git rebase` in interactive mode.
-> See the [git docs](https://git-scm.com/docs/git-rebase#_interactive_mode) for more details.
-
-
 #### After your pull request is merged
 
-After your pull request is merged, you can safely delete your branch and pull the changes from the main (upstream) repository:
+After your pull request is merged, you can safely delete your branch and pull the changes
+from the main (upstream) repository:
 
 * Delete the remote branch on GitHub either through the GitHub web UI or your local shell as follows:
 
@@ -181,10 +123,10 @@ After your pull request is merged, you can safely delete your branch and pull th
     git push origin --delete my-fix-branch
     ```
 
-* Check out the main branch:
+* Check out the master branch:
 
     ```shell
-    git checkout main -f
+    git checkout master -f
     ```
 
 * Delete the local branch:
@@ -193,207 +135,160 @@ After your pull request is merged, you can safely delete your branch and pull th
     git branch -D my-fix-branch
     ```
 
-* Update your local `main` with the latest upstream version:
+* Update your master with the latest upstream version:
 
     ```shell
-    git pull --ff upstream main
+    git pull --ff upstream master
     ```
 
-
 ## <a name="rules"></a> Coding Rules
 To ensure consistency throughout the source code, keep these rules in mind as you are working:
 
 * All features or bug fixes **must be tested** by one or more specs (unit-tests).
-* All public API methods **must be documented**.
-* We follow [Google's JavaScript Style Guide][js-style-guide], but wrap all code at **100 characters**.
+* All public API methods **must be documented**. (Details TBC).
+* We follow [Google's JavaScript Style Guide][js-style-guide], but wrap all code at
+  **100 characters**. An automated formatter is available, see
+  [DEVELOPER.md](docs/DEVELOPER.md#clang-format).
 
-   An automated formatter is available, see [DEVELOPER.md](contributing-docs/building-and-testing-angular.md#formatting-your-source-code).
+## <a name="commit"></a> Commit Message Guidelines
 
+We have very precise rules over how our git commit messages can be formatted.  This leads to **more
+readable messages** that are easy to follow when looking through the **project history**.  But also,
+we use the git commit messages to **generate the Angular change log**.
 
-## <a name="commit"></a> Commit Message Format
-
-*This specification is inspired by and supersedes the [AngularJS commit message format][commit-message-format].*
-
-We have very precise rules over how our Git commit messages must be formatted.
-This format leads to **easier to read commit history**.
-
-Each commit message consists of a **header**, a **body**, and a **footer**.
-
+### Commit Message Format
+Each commit message consists of a **header**, a **body** and a **footer**.  The header has a special
+format that includes a **type**, a **scope** and a **subject**:
 
 ```
-<header>
+<type>(<scope>): <subject>
 <BLANK LINE>
 <body>
 <BLANK LINE>
 <footer>
 ```
 
-The `header` is mandatory and must conform to the [Commit Message Header](#commit-header) format.
+The **header** is mandatory and the **scope** of the header is optional.
 
-The `body` is mandatory for all commits except for those of type "docs".
-When the body is present it must be at least 20 characters long and must conform to the [Commit Message Body](#commit-body) format.
+Any line of the commit message cannot be longer 100 characters! This allows the message to be easier
+to read on GitHub as well as in various git tools.
 
-The `footer` is optional. The [Commit Message Footer](#commit-footer) format describes what the footer is used for and the structure it must have.
+The footer should contain a [closing reference to an issue](https://help.github.com/articles/closing-issues-via-commit-messages/) if any.
 
-
-#### <a name="commit-header"></a>Commit Message Header
+Samples: (even more [samples](https://github.com/angular/angular/commits/master))
 
 ```
-<type>(<scope>): <short summary>
-  │       │             │
-  │       │             └─⫸ Summary in present tense. Not capitalized. No period at the end.
-  │       │
-  │       └─⫸ Commit Scope: animations|bazel|benchpress|common|compiler|compiler-cli|core|
-  │                          elements|forms|http|language-service|localize|platform-browser|
-  │                          platform-browser-dynamic|platform-server|router|service-worker|
-  │                          upgrade|zone.js|packaging|changelog|docs-infra|migrations|
-  │                          devtools
-  │
-  └─⫸ Commit Type: build|ci|docs|feat|fix|perf|refactor|test
+docs(changelog): update changelog to beta.5
+```
+```
+fix(release): need to depend on latest rxjs and zone.js
+
+The version in our package.json gets copied to the one we publish, and users need the latest of these.
 ```
 
-The `<type>` and `<summary>` fields are mandatory, the `(<scope>)` field is optional.
-
-
-##### Type
+### Revert
+If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of the reverted commit. In the body it should say: `This reverts commit <hash>.`, where the hash is the SHA of the commit being reverted.
 
+### Type
 Must be one of the following:
 
 * **build**: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
-* **ci**: Changes to our CI configuration files and scripts (examples: CircleCi, SauceLabs)
+* **ci**: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 * **docs**: Documentation only changes
 * **feat**: A new feature
 * **fix**: A bug fix
 * **perf**: A code change that improves performance
 * **refactor**: A code change that neither fixes a bug nor adds a feature
+* **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 * **test**: Adding missing tests or correcting existing tests
 
-
-##### Scope
-The scope should be the name of the npm package affected (as perceived by the person reading the changelog generated from commit messages).
+### Scope
+The scope should be the name of the npm package affected (as perceived by the person reading the changelog generated from commit messages.
 
 The following is the list of supported scopes:
 
-* `animations`
-* `bazel`
-* `benchpress`
-* `common`
-* `compiler`
-* `compiler-cli`
-* `core`
-* `elements`
-* `forms`
-* `http`
-* `language-service`
-* `localize`
-* `platform-browser`
-* `platform-browser-dynamic`
-* `platform-server`
-* `router`
-* `service-worker`
-* `upgrade`
-* `zone.js`
+* **animations**
+* **common**
+* **compiler**
+* **compiler-cli**
+* **core**
+* **elements**
+* **forms**
+* **http**
+* **language-service**
+* **platform-browser**
+* **platform-browser-dynamic**
+* **platform-server**
+* **platform-webworker**
+* **platform-webworker-dynamic**
+* **router**
+* **service-worker**
+* **upgrade**
 
 There are currently a few exceptions to the "use package name" rule:
 
-* `packaging`: used for changes that change the npm package layout in all of our packages, e.g. public path changes, package.json changes done to all packages, d.ts file/format changes, changes to bundles, etc.
+* **packaging**: used for changes that change the npm package layout in all of our packages, e.g.
+  public path changes, package.json changes done to all packages, d.ts file/format changes, changes
+  to bundles, etc.
+* **changelog**: used for updating the release notes in CHANGELOG.md
+* **docs-infra**: used for docs-app (angular.io) related changes within the /aio directory of the
+  repo
+* none/empty string: useful for `style`, `test` and `refactor` changes that are done across all
+  packages (e.g. `style: add missing semicolons`) and for docs changes that are not related to a
+  specific package (e.g. `docs: fix typo in tutorial`).
 
-* `changelog`: used for updating the release notes in CHANGELOG.md
-
-* `dev-infra`: used for dev-infra related changes within the directories /scripts and /tools
-
-* `docs-infra`: used for docs-app (angular.dev) related changes within the /adev directory of the repo
-
-* `migrations`: used for changes to the `ng update` migrations.
-
-* `devtools`: used for changes in the [browser extension](./devtools/README.md).
-
-* none/empty string: useful for `test` and `refactor` changes that are done across all packages (e.g. `test: add missing unit tests`) and for docs changes that are not related to a specific package (e.g. `docs: fix typo in tutorial`).
-
-
-##### Summary
-
-Use the summary field to provide a succinct description of the change:
+### Subject
+The subject contains a succinct description of the change:
 
 * use the imperative, present tense: "change" not "changed" nor "changes"
 * don't capitalize the first letter
 * no dot (.) at the end
 
+### Body
+Just as in the **subject**, use the imperative, present tense: "change" not "changed" nor "changes".
+The body should include the motivation for the change and contrast this with previous behavior.
 
-#### <a name="commit-body"></a>Commit Message Body
+### Footer
+The footer should contain any information about **Breaking Changes** and is also the place to
+reference GitHub issues that this commit **Closes**.
 
-Just as in the summary, use the imperative, present tense: "fix" not "fixed" nor "fixes".
-
-Explain the motivation for the change in the commit message body. This commit message should explain _why_ you are making the change.
-You can include a comparison of the previous behavior with the new behavior in order to illustrate the impact of the change.
-
-
-#### <a name="commit-footer"></a>Commit Message Footer
-
-The footer can contain information about breaking changes and deprecations and is also the place to reference GitHub issues, Jira tickets, and other PRs that this commit closes or is related to.
-For example:
-
-```
-BREAKING CHANGE: <breaking change summary>
-<BLANK LINE>
-<breaking change description + migration instructions>
-<BLANK LINE>
-<BLANK LINE>
-Fixes #<issue number>
-```
-
-or
-
-```
-DEPRECATED: <what is deprecated>
-<BLANK LINE>
-<deprecation description + recommended update path>
-<BLANK LINE>
-<BLANK LINE>
-Closes #<pr number>
-```
-
-Breaking Change section should start with the phrase `BREAKING CHANGE: ` followed by a summary of the breaking change, a blank line, and a detailed description of the breaking change that also includes migration instructions.
-
-Similarly, a Deprecation section should start with `DEPRECATED: ` followed by a short description of what is deprecated, a blank line, and a detailed description of the deprecation that also mentions the recommended update path.
-
-
-### Revert commits
-
-If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of the reverted commit.
-
-The content of the commit message body should contain:
-
-- information about the SHA of the commit being reverted in the following format: `This reverts commit <SHA>`,
-- a clear description of the reason for reverting the commit message.
+**Breaking Changes** should start with the word `BREAKING CHANGE:` with a space or two newlines. The rest of the commit message is then used for this.
 
+A detailed explanation can be found in this [document][commit-message-format].
 
 ## <a name="cla"></a> Signing the CLA
 
 Please sign our Contributor License Agreement (CLA) before sending pull requests. For any code
 changes to be accepted, the CLA must be signed. It's a quick process, we promise!
 
-* For individuals, we have a [simple click-through form][individual-cla].
-* For corporations, we'll need you to
+* For individuals we have a [simple click-through form][individual-cla].
+* For corporations we'll need you to
   [print, sign and one of scan+email, fax or mail the form][corporate-cla].
 
-If you have more than one GitHub accounts, or multiple email addresses associated with a single GitHub account, you must sign the CLA using the primary email address of the GitHub account used to author Git commits and send pull requests.
+<hr>
 
-The following documents can help you sort out issues with GitHub accounts and multiple email addresses:
+  If you have more than one Git identity, you must make sure that you sign the CLA using the primary email address associated with the ID that has been granted access to the Angular repository. Git identities can be associated with more than one email address, and only one is primary. Here are some links to help you sort out multiple Git identities and email addresses:
 
   * https://help.github.com/articles/setting-your-commit-email-address-in-git/
   * https://stackoverflow.com/questions/37245303/what-does-usera-committed-with-userb-13-days-ago-on-github-mean
   * https://help.github.com/articles/about-commit-email-addresses/
   * https://help.github.com/articles/blocking-command-line-pushes-that-expose-your-personal-email-address/
 
+  Note that if you have more than one Git identity, it is important to verify that you are logged in with the same ID with which you signed the CLA, before you commit changes. If not, your PR will fail the CLA check.
+
+<hr>
 
 
-
-[coc]: https://github.com/angular/code-of-conduct/blob/main/CODE_OF_CONDUCT.md
+[angular-group]: https://groups.google.com/forum/#!forum/angular
+[coc]: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md
 [commit-message-format]: https://docs.google.com/document/d/1QrDFcIiPjSLDn3EL15IJygNPiHORgU1_OOAqWjiDU5Y/edit#
-[corporate-cla]: https://cla.developers.google.com/about/google-corporate
-[dev-doc]: ./contributing-docs/building-and-testing-angular.md
+[corporate-cla]: http://code.google.com/legal/corporate-cla-v1.0.html
+[dev-doc]: https://github.com/angular/angular/blob/master/docs/DEVELOPER.md
 [github]: https://github.com/angular/angular
-[discord]: https://discord.gg/angular
-[individual-cla]: https://cla.developers.google.com/about/google-individual
+[gitter]: https://gitter.im/angular/angular
+[individual-cla]: http://code.google.com/legal/individual-cla-v1.0.html
 [js-style-guide]: https://google.github.io/styleguide/jsguide.html
+[jsfiddle]: http://jsfiddle.net
+[plunker]: http://plnkr.co/edit
+[runnable]: http://runnable.com
+[stackoverflow]: http://stackoverflow.com/questions/tagged/angular

LICENSE

@@ -1,6 +1,6 @@
 The MIT License
 
-Copyright (c) 2010-2024 Google LLC. https://angular.dev/license
+Copyright (c) 2014-2018 Google, Inc. http://angular.io
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

README.md

@@ -1,171 +1,31 @@
-<h1 align="center">Angular - The modern web developer's platform</h1>
+[![Build Status](https://travis-ci.org/angular/angular.svg?branch=master)](https://travis-ci.org/angular/angular)
+[![CircleCI](https://circleci.com/gh/angular/angular/tree/master.svg?style=shield)](https://circleci.com/gh/angular/angular/tree/master)
+[![BrowserStack Status](https://www.browserstack.com/automate/badge.svg?badge_key=LzF3RzBVVGt6VWE2S0hHaC9uYllOZz09LS1BVjNTclBKV0x4eVRlcjA4QVY1M0N3PT0=--eb4ce8c8dc2c1c5b2b5352d473ee12a73ac20e06)](https://www.browserstack.com/automate/public-build/LzF3RzBVVGt6VWE2S0hHaC9uYllOZz09LS1BVjNTclBKV0x4eVRlcjA4QVY1M0N3PT0=--eb4ce8c8dc2c1c5b2b5352d473ee12a73ac20e06)
+[![Join the chat at https://gitter.im/angular/angular](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/angular/angular?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
+[![npm version](https://badge.fury.io/js/%40angular%2Fcore.svg)](https://www.npmjs.com/@angular/core)
 
-<p align="center">
-  <img src="adev/src/assets/images/press-kit/angular_icon_gradient.gif" alt="angular-logo" width="120px" height="120px"/>
-  <br>
-  <em>Angular is a development platform for building mobile and desktop web applications
-    <br> using TypeScript/JavaScript and other languages.</em>
-  <br>
-</p>
 
-<p align="center">
-  <a href="https://angular.dev/"><strong>angular.dev</strong></a>
-  <br>
-</p>
+# Angular
 
-<p align="center">
-  <a href="CONTRIBUTING.md">Contributing Guidelines</a>
-  ·
-  <a href="https://github.com/angular/angular/issues">Submit an Issue</a>
-  ·
-  <a href="https://blog.angular.dev/">Blog</a>
-  <br>
-  <br>
-</p>
-
-<p align="center">
-  <a href="https://circleci.com/gh/angular/workflows/angular/tree/main">
-    <img src="https://img.shields.io/circleci/build/github/angular/angular/main.svg?logo=circleci&logoColor=fff&label=CircleCI" alt="CI status" />
-  </a>&nbsp;
-  <a href="https://www.npmjs.com/@angular/core">
-    <img src="https://img.shields.io/npm/v/@angular/core.svg?logo=npm&logoColor=fff&label=NPM+package&color=limegreen" alt="Angular on npm" />
-  </a>&nbsp;
-  <a href="https://discord.gg/angular">
-    <img src="https://img.shields.io/discord/463752820026376202.svg?logo=discord&logoColor=fff&label=Discord&color=7389d8" alt="Discord conversation" />
-  </a>
-</p>
-
-<p align="center">
-  <a href="https://app.circleci.com/insights/github/angular/angular/workflows/default_workflow?branch=main">
-    <img src="https://dl.circleci.com/insights-snapshot/gh/angular/angular/main/default_workflow/badge.svg" alt="InsightsSnapshot" />
-  </a>
-</p>
-
-<hr>
-
-## Documentation
-
-Get started with Angular, learn the fundamentals and explore advanced topics on our documentation website.
-
-- [Getting Started][quickstart]
-- [Architecture][architecture]
-- [Components and Templates][componentstemplates]
-- [Forms][forms]
-- [API][api]
-
-### Advanced
-
-- [Angular Elements][angularelements]
-- [Server Side Rendering][ssr]
-- [Schematics][schematics]
-- [Lazy Loading][lazyloading]
-- [Animations][animations]
-
-### Local Development
-
-To contribute to the Angular Docs, check out the [Angular.dev README](adev/README.md)
-
-## Development Setup
-
-### Prerequisites
-
-- Install [Node.js] which includes [Node Package Manager][npm]
-
-### Setting Up a Project
-
-Install the Angular CLI globally:
-
-```
-npm install -g @angular/cli
-```
-
-Create workspace:
-
-```
-ng new [PROJECT NAME]
-```
-
-Run the application:
-
-```
-cd [PROJECT NAME]
-ng serve
-```
-
-Angular is cross-platform, fast, scalable, has incredible tooling, and is loved by millions.
+Angular is a development platform for building mobile and desktop web applications using Typescript/JavaScript and other languages.
 
 ## Quickstart
 
 [Get started in 5 minutes][quickstart].
 
-## Ecosystem
-
-<p>
-  <img src="/contributing-docs/images/angular-ecosystem-logos.png" alt="angular ecosystem logos" width="500px" height="auto">
-</p>
-
-- [Angular Command Line (CLI)][cli]
-- [Angular Material][angularmaterial]
 
 ## Changelog
 
-[Learn about the latest improvements][changelog].
+[Learn about the latest improvements][changelog]. 
 
-## Upgrading
 
-Check out our [upgrade guide](https://angular.dev/update-guide/) to find out the best way to upgrade your project.
+## Want to help?
 
-## Contributing
+Want to file a bug, contribute some code, or improve documentation? Excellent! Read up on our
+guidelines for [contributing][contributing] and then check out one of our issues in the [hotlist: community-help](https://github.com/angular/angular/labels/hotlist%3A%20community-help).
 
-### Contributing Guidelines
-
-Read through our [contributing guidelines][contributing] to learn about our submission process, coding rules, and more.
-
-### Want to Help?
-
-Want to report a bug, contribute some code, or improve the documentation? Excellent! Read up on our guidelines for [contributing][contributing] and then check out one of our issues labeled as <kbd>[help wanted](https://github.com/angular/angular/labels/help%20wanted)</kbd> or <kbd>[good first issue](https://github.com/angular/angular/labels/good%20first%20issue)</kbd>.
-
-### Code of Conduct
-
-Help us keep Angular open and inclusive. Please read and follow our [Code of Conduct][codeofconduct].
-
-## Community
-
-Join the conversation and help the community.
-
-- [X (formerly Twitter)][X (formerly Twitter)]
-- [Discord][discord]
-- [Gitter][gitter]
-- [YouTube][youtube]
-- [StackOverflow][stackoverflow]
-- Find a Local [Meetup][meetup]
-
-[![Love Angular badge](https://img.shields.io/badge/angular-love-blue?logo=angular&angular=love)](https://www.github.com/angular/angular)
-
-**Love Angular? Give our repo a star :star: :arrow_up:.**
-
-[contributing]: CONTRIBUTING.md
-[quickstart]: https://angular.dev/tutorials/learn-angular
-[changelog]: CHANGELOG.md
-[ng]: https://angular.dev
-[documentation]: https://angular.dev/overview
-[angularmaterial]: https://material.angular.io/
-[cli]: https://angular.dev/tools/cli
-[architecture]: https://angular.dev/essentials
-[componentstemplates]: https://angular.dev/tutorials/learn-angular/1-components-in-angular
-[forms]: https://angular.dev/tutorials/learn-angular/15-forms
-[api]: https://angular.dev/api
-[angularelements]: https://angular.dev/guide/elements
-[ssr]: https://angular.dev/guide/ssr
-[schematics]: https://angular.dev/tools/cli/schematics
-[lazyloading]: https://angular.dev/guide/ngmodules/lazy-loading
-[node.js]: https://nodejs.org/
-[npm]: https://www.npmjs.com/get-npm
-[codeofconduct]: CODE_OF_CONDUCT.md
-[X (formerly Twitter)]: https://www.twitter.com/angular
-[discord]: https://discord.gg/angular
-[gitter]: https://gitter.im/angular/angular
-[stackoverflow]: https://stackoverflow.com/questions/tagged/angular
-[youtube]: https://youtube.com/angular
-[meetup]: https://www.meetup.com/find/?keywords=angular
-[animations]: https://angular.dev/guide/animations
+[browserstack]: https://www.browserstack.com/automate/public-build/LzF3RzBVVGt6VWE2S0hHaC9uYllOZz09LS1BVjNTclBKV0x4eVRlcjA4QVY1M0N3PT0=--eb4ce8c8dc2c1c5b2b5352d473ee12a73ac20e06
+[contributing]: https://github.com/angular/angular/blob/master/CONTRIBUTING.md
+[quickstart]: https://angular.io/guide/quickstart
+[changelog]: https://github.com/angular/angular/blob/master/CHANGELOG.md
+[ng]: https://angular.io

SECURITY.md

@@ -1,3 +0,0 @@
-Angular is part of Google [Open Source Software Vulnerability Reward Program](https://bughunters.google.com/about/rules/6521337925468160/google-open-source-software-vulnerability-reward-program-rules). For vulnerabilities in Angular, please submit your report [here](https://bughunters.google.com/report).
-
-For more information, check out [Angular's security policy](https://angular.dev/best-practices/security).

WORKSPACE

@@ -1,195 +1,87 @@
-workspace(
-    name = "angular",
-    managed_directories = {
-        "@npm": ["node_modules"],
-    },
+workspace(name = "angular")
+
+load(
+    "//packages/bazel:package.bzl",
+    "rules_angular_dependencies",
+    "rules_angular_dev_dependencies",
 )
 
-load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
-load("//:yarn.bzl", "YARN_LABEL")
+# Angular Bazel users will call this function
+rules_angular_dependencies()
+# These are the dependencies only for us
+rules_angular_dev_dependencies()
 
+#
+# Point Bazel to WORKSPACEs that live in subdirectories
+#
 http_archive(
-    name = "build_bazel_rules_nodejs",
-    patches = [
-        "//tools/esm-interop:patches/bazel/nodejs_binary_esm_support.patch",
-    ],
-    sha256 = "5dd1e5dea1322174c57d3ca7b899da381d516220793d0adef3ba03b9d23baa8e",
-    urls = ["https://github.com/bazelbuild/rules_nodejs/releases/download/5.8.3/rules_nodejs-5.8.3.tar.gz"],
+    name = "rxjs",
+    url = "https://registry.yarnpkg.com/rxjs/-/rxjs-6.3.3.tgz",
+    strip_prefix = "package/src",
+    sha256 = "72b0b4e517f43358f554c125e40e39f67688cd2738a8998b4a266981ed32f403",
 )
 
-load("@build_bazel_rules_nodejs//:repositories.bzl", "build_bazel_rules_nodejs_dependencies")
-
-build_bazel_rules_nodejs_dependencies()
-
-# The PKG rules are needed to build tar packages for integration tests. The builtin
-# rule in `@bazel_tools` is not Windows compatible and outdated.
-# NOTE: We cannot move past version 0.6.0 as pkg_tar no longer works on directories, which rules_nodejs
-#       relies on for node_modules setup.
-http_archive(
-    name = "rules_pkg",
-    sha256 = "62eeb544ff1ef41d786e329e1536c1d541bb9bcad27ae984d57f18f314018e66",
-    urls = [
-        "https://mirror.bazel.build/github.com/bazelbuild/rules_pkg/releases/download/0.6.0/rules_pkg-0.6.0.tar.gz",
-        "https://github.com/bazelbuild/rules_pkg/releases/download/0.6.0/rules_pkg-0.6.0.tar.gz",
-    ],
+# Point to the integration test workspace just so that Bazel doesn't descend into it
+# when expanding the //... pattern
+local_repository(
+    name = "bazel_integration_test",
+    path = "integration/bazel",
 )
 
-# Fetch Aspect lib for utilities like write_source_files
-# NOTE: We cannot move past version 1.23.2 of aspect_bazel_lib because it requires us to move to bazel 6.0.0 which
-#       breaks our usage of managed_directories
-http_archive(
-    name = "aspect_bazel_lib",
-    sha256 = "4b2e774387bae6242879820086b7b738d49bf3d0659522ea5d9363be01a27582",
-    strip_prefix = "bazel-lib-1.23.2",
-    url = "https://github.com/aspect-build/bazel-lib/archive/refs/tags/v1.23.2.tar.gz",
+#
+# Load and install our dependencies downloaded above.
+#
+load("@build_bazel_rules_nodejs//:defs.bzl", "check_bazel_version", "node_repositories", "yarn_install")
+
+check_bazel_version("0.18.0", """
+If you are on a Mac and using Homebrew, there is a breaking change to the installation in Bazel 0.16
+See https://blog.bazel.build/2018/08/22/bazel-homebrew.html
+
+""")
+
+node_repositories(
+    node_version = "10.9.0",
+    package_json = ["//:package.json"],
+    preserve_symlinks = True,
+    yarn_version = "1.9.2",
 )
 
-# Setup the Node.js toolchain.
-load("@rules_nodejs//nodejs:repositories.bzl", "nodejs_register_toolchains")
-
-nodejs_register_toolchains(
-    name = "nodejs",
-    node_repositories = {
-        "18.20.0-darwin_arm64": ("node-v18.20.0-darwin-arm64.tar.gz", "node-v18.20.0-darwin-arm64", "10066ad4dd9e03ea5c4c45ef8775420ff37b860de09bbdf87b97e0c07b1ea036"),
-        "18.20.0-darwin_amd64": ("node-v18.20.0-darwin-x64.tar.gz", "node-v18.20.0-darwin-x64", "062ba71618e88e06321de5caa038843c350aababa2d315f3ca7b8551f8e66c1c"),
-        "18.20.0-linux_arm64": ("node-v18.20.0-linux-arm64.tar.xz", "node-v18.20.0-linux-arm64", "afe51da9ffb38ac1e3a20d9a06efd403ced4bf8831ab554a02a088dd8392fd79"),
-        "18.20.0-linux_ppc64le": ("node-v18.20.0-linux-ppc64le.tar.xz", "node-v18.20.0-linux-ppc64le", "9e652bbf53a3e37285b11dfb9d6a9bb8b02010c3b50e5c8229d4cc10e72681da"),
-        "18.20.0-linux_s390x": ("node-v18.20.0-linux-s390x.tar.xz", "node-v18.20.0-linux-s390x", "a6c2a5796b9d9e9bf21da62ec89ff30b41a8108880b9eaa3c912f1ce795a7743"),
-        "18.20.0-linux_amd64": ("node-v18.20.0-linux-x64.tar.xz", "node-v18.20.0-linux-x64", "03eea148e56785babb27930b05ed6bf311aaa3bc573c0399dd63cad2fe5713c7"),
-        "18.20.0-windows_amd64": ("node-v18.20.0-win-x64.zip", "node-v18.20.0-win-x64", "1c0aab05cc6836a8f5148cca345b92ebc948a4a2013f18d117b7ade6ff05aca6"),
-    },
-    # We need at least Node 18.17 due to some transitive dependencies.
-    node_version = "18.20.0",
-)
-
-# Download npm dependencies.
-load("@build_bazel_rules_nodejs//:index.bzl", "yarn_install")
-load("//integration:npm_package_archives.bzl", "npm_package_archives")
-
 yarn_install(
     name = "npm",
-    # Note that we add the postinstall scripts here so that the dependencies are re-installed
-    # when the postinstall patches are modified.
-    data = [
-        YARN_LABEL,
-        "//:.yarnrc",
-        "//:tools/npm-patches/@bazel+jasmine+5.8.1.patch",
-        "//tools:postinstall-patches.js",
-        "//tools/esm-interop:patches/npm/@angular+build-tooling+0.0.0-d30a56c19bafaac67cf44e605ed8c2c0e45b0a51.patch",
-        "//tools/esm-interop:patches/npm/@bazel+concatjs+5.8.1.patch",
-        "//tools/esm-interop:patches/npm/@bazel+esbuild+5.7.1.patch",
-        "//tools/esm-interop:patches/npm/@bazel+protractor+5.7.1.patch",
-        "//tools/esm-interop:patches/npm/rxjs+6.6.7.patch",
-    ],
-    # Currently disabled due to:
-    #  1. Missing Windows support currently.
-    #  2. Incompatibilites with the `ts_library` rule.
-    exports_directories_only = False,
-    manual_build_file_contents = npm_package_archives(),
-    package_json = "//:package.json",
-    # We prefer to symlink the `node_modules` to only maintain a single install.
-    # See https://github.com/angular/dev-infra/pull/446#issuecomment-1059820287 for details.
-    symlink_node_modules = True,
-    yarn = YARN_LABEL,
-    yarn_lock = "//:yarn.lock",
+    package_json = "//tools:npm/package.json",
+    yarn_lock = "//tools:npm/yarn.lock",
 )
 
-load("@aspect_bazel_lib//lib:repositories.bzl", "aspect_bazel_lib_dependencies")
+load("@io_bazel_rules_go//go:def.bzl", "go_rules_dependencies", "go_register_toolchains")
 
-aspect_bazel_lib_dependencies()
+go_rules_dependencies()
 
-# Load protractor dependencies
-load("@npm//@bazel/protractor:package.bzl", "npm_bazel_protractor_dependencies")
+go_register_toolchains()
 
-npm_bazel_protractor_dependencies()
-
-# Setup the rules_webtesting toolchain
-load("@io_bazel_rules_webtesting//web:repositories.bzl", "web_test_repositories")
+load("@io_bazel_rules_webtesting//web:repositories.bzl", "browser_repositories", "web_test_repositories")
 
 web_test_repositories()
 
-load("@npm//@angular/build-tooling/bazel/browsers:browser_repositories.bzl", "browser_repositories")
-
-browser_repositories()
-
-load("@build_bazel_rules_nodejs//toolchains/esbuild:esbuild_repositories.bzl", "esbuild_repositories")
-
-esbuild_repositories(
-    npm_repository = "npm",
+browser_repositories(
+    chromium = True,
+    firefox = True,
 )
 
-load("@rules_pkg//:deps.bzl", "rules_pkg_dependencies")
+load("@build_bazel_rules_typescript//:defs.bzl", "ts_setup_workspace")
 
-rules_pkg_dependencies()
+ts_setup_workspace()
 
-load("//packages/common/locales/generate-locales-tool:cldr-data.bzl", "cldr_json_data_repository", "cldr_xml_data_repository")
+load("@angular//:index.bzl", "ng_setup_workspace")
 
-cldr_major_version = "41"
+ng_setup_workspace()
 
-cldr_json_data_repository(
-    name = "cldr_json_data",
-    urls = {
-        "https://github.com/unicode-org/cldr-json/releases/download/%s.0.0/cldr-%s.0.0-json-full.zip" % (cldr_major_version, cldr_major_version): "649b76647269e32b1b0a5f7b6eed52e9e63a1581f1afdcf4f6771e49c9713614",
-    },
-)
+##################################
+# Skylark documentation generation
 
-cldr_xml_data_repository(
-    name = "cldr_xml_data",
-    urls = {
-        "https://github.com/unicode-org/cldr/releases/download/release-%s/cldr-common-%s.0.zip" % (cldr_major_version, cldr_major_version): "823c6170c41e2de2c229574e8a436332d25f1c9723409867fe721e00bc92d853",
-    },
-)
-
-# sass rules
-http_archive(
-    name = "io_bazel_rules_sass",
-    sha256 = "b00f13a280fc60ef2a1d142b31c629075bac841c980a0c3462190f338e5d584a",
-    strip_prefix = "rules_sass-6e23fb1351f392f7fe7a07038cd537770fe97742",
-    urls = [
-        "https://github.com/bazelbuild/rules_sass/archive/6e23fb1351f392f7fe7a07038cd537770fe97742.zip",
-    ],
-)
-
-# Setup the rules_sass toolchain
 load("@io_bazel_rules_sass//sass:sass_repositories.bzl", "sass_repositories")
 
-sass_repositories(
-    yarn_script = YARN_LABEL,
-)
+sass_repositories()
 
-# Register git toolchains
-register_toolchains(
-    "@npm//@angular/build-tooling/bazel/git-toolchain:git_linux_toolchain",
-    "@npm//@angular/build-tooling/bazel/git-toolchain:git_macos_x86_toolchain",
-    "@npm//@angular/build-tooling/bazel/git-toolchain:git_macos_arm64_toolchain",
-    "@npm//@angular/build-tooling/bazel/git-toolchain:git_windows_toolchain",
-)
+load("@io_bazel_skydoc//skylark:skylark.bzl", "skydoc_repositories")
 
-# Fetch sauce connect (tool to open Saucelabs tunnel for Saucelabs browser tests)
-http_archive(
-    name = "sauce_connect_linux_amd64",
-    build_file_content = """exports_files(["bin/sc"], visibility = ["//visibility:public"])""",
-    sha256 = "26b9c3630f441b47854b6032f7eca6f1d88d3f62e50ee44c27015d71a5155c36",
-    strip_prefix = "sc-4.8.2-linux",
-    url = "https://saucelabs.com/downloads/sc-4.8.2-linux.tar.gz",
-)
-
-http_archive(
-    name = "sauce_connect_mac",
-    build_file_content = """exports_files(["bin/sc"], visibility = ["//visibility:public"])""",
-    sha256 = "28277ce81ef9ab84f5b87b526258920a8ead44789a5034346e872629bbf38089",
-    strip_prefix = "sc-4.8.2-osx",
-    url = "https://saucelabs.com/downloads/sc-4.8.2-osx.zip",
-)
-
-yarn_install(
-    name = "npm_ts_versions",
-    data = [
-        YARN_LABEL,
-        "//:.yarnrc",
-    ],
-    exports_directories_only = False,
-    package_json = "//packages/core/schematics/migrations/signal-migration/test/ts-versions:package.json",
-    yarn = YARN_LABEL,
-    yarn_lock = "//packages/core/schematics/migrations/signal-migration/test/ts-versions:yarn.lock",
-)
+skydoc_repositories()

adev/BUILD.bazel

@@ -1,187 +0,0 @@
-load("@npm//@angular/build-tooling/bazel/remote-execution:index.bzl", "ENABLE_NETWORK")
-load("@npm//@angular/build-tooling/bazel/http-server:index.bzl", "http_server")
-load("@bazel_skylib//rules:common_settings.bzl", "bool_flag")
-load("@build_bazel_rules_nodejs//:index.bzl", "copy_to_bin")
-load("@npm//@angular-devkit/architect-cli:index.bzl", "architect", "architect_test")
-load("@bazel_skylib//lib:collections.bzl", "collections")
-load("//adev/tools/local_deps:index.bzl", "ensure_local_package_deps", "link_local_packages")
-
-package(default_visibility = ["//visibility:public"])
-
-exports_files([
-    "tsconfig.json",
-])
-
-# All source and configuration files required to build the docs app
-APPLICATION_FILES = [
-    "angular.json",
-    "tsconfig.app.json",
-    "tsconfig.json",
-    "tsconfig.worker.json",
-] + glob(
-    ["src/**/*"],
-    exclude = [
-        "src/**/*.spec.ts",
-    ],
-)
-
-TEST_FILES = APPLICATION_FILES + [
-    "karma.conf.js",
-    "test-main.ts",
-    "tsconfig.spec.json",
-] + glob(
-    ["src/**/*.spec.ts"],
-)
-
-APPLICATION_ASSETS = [
-    "//adev/src/assets/images",
-    "//adev/src/assets/textures",
-    "//adev/src/assets/previews",
-    "//adev/src/assets:tutorials",
-    "//adev/src/assets/icons",
-    "//adev/src/assets:api",
-    "//adev/src/assets:content",
-]
-
-APPLICATION_DEPS = [
-    "@npm//@angular/docs",
-    "@npm//@angular/build",
-    "@npm//@angular-devkit/build-angular",
-    "@npm//@angular/animations",
-    "@npm//@angular/cdk",
-    "@npm//@angular/common",
-    "@npm//@angular/compiler",
-    "@npm//@angular/compiler-cli",
-    "@npm//@angular/core",
-    "@npm//@angular/forms",
-    "@npm//@angular/material",
-    "@npm//@angular/platform-browser",
-    "@npm//@angular/platform-server",
-    "@npm//@angular/router",
-    "@npm//gsap",
-    "@npm//marked",
-    "@npm//ngx-progressbar",
-    "@npm//ogl",
-    "@npm//rxjs",
-    "@npm//typescript",
-    "@npm//@typescript/vfs",
-    "@npm//@codemirror/state",
-    "@npm//@codemirror/view",
-    "@npm//@codemirror/language",
-    "@npm//@codemirror/commands",
-    "@npm//@codemirror/search",
-    "@npm//@codemirror/autocomplete",
-    "@npm//@codemirror/lint",
-    "@npm//@codemirror/lang-html",
-    "@npm//@codemirror/lang-angular",
-    "@npm//@codemirror/lang-css",
-    "@npm//@codemirror/lang-sass",
-    "@npm//@codemirror/lang-javascript",
-    "@npm//@lezer/highlight",
-    "@npm//@lezer/javascript",
-    "@npm//@lezer/common",
-    "@npm//@stackblitz/sdk",
-    "@npm//open-in-idx",
-    "@npm//@webcontainer/api",
-    "@npm//@xterm/xterm",
-    "@npm//@xterm/addon-fit",
-    "@npm//algoliasearch",
-    "@npm//angular-split",
-    "@npm//zone.js",
-]
-
-TEST_DEPS = APPLICATION_DEPS + [
-    "@npm//@angular/platform-browser-dynamic",
-    "@npm//@types/jasmine",
-    "@npm//@types/node",
-    "@npm//jasmine",
-    "@npm//jasmine-core",
-    "@npm//karma-chrome-launcher",
-    "@npm//karma-coverage",
-    "@npm//karma-jasmine",
-    "@npm//karma-jasmine-html-reporter",
-]
-
-# Create `npm_link` targets for all dependencies that correspond to a
-# first-party Angular package that can be built from `HEAD`.
-link_local_packages(
-    all_deps = collections.uniq(APPLICATION_DEPS + TEST_DEPS),
-)
-
-copy_to_bin(
-    name = "application_files_bin",
-    srcs = APPLICATION_FILES,
-)
-
-bool_flag(
-    name = "prerender_adev",
-    build_setting_default = False,
-)
-
-config_setting(
-    name = "no_prerender",
-    flag_values = {
-        ":prerender_adev": "false",
-    },
-)
-
-config_setting(
-    name = "prerender",
-    flag_values = {
-        ":prerender_adev": "true",
-    },
-)
-
-config_based_architect_flags = select({
-    ":no_prerender": ["--no-prerender"],
-    ":prerender": ["--prerender"],
-})
-
-architect(
-    name = "build",
-    args = [
-        "angular-dev:build",
-        "--output-path=build",
-    ] + config_based_architect_flags,
-    chdir = "$(RULEDIR)",
-    data = ensure_local_package_deps(APPLICATION_DEPS) + APPLICATION_ASSETS + [
-        ":application_files_bin",
-    ],
-    env = {
-        "NG_BUILD_OPTIMIZE_CHUNKS": "1",
-    },
-    # Network is required to inline fonts.
-    exec_properties = ENABLE_NETWORK,
-    output_dir = True,
-    tags = [
-        "no-remote-exec",
-    ],
-)
-
-http_server(
-    name = "serve",
-    additional_root_paths = [
-        "angular/adev/build/browser",
-    ],
-    enable_dev_ui = True,
-    deps = [":build"],
-)
-
-architect_test(
-    name = "test",
-    args = [
-        "angular-dev:test",
-        "--no-watch",
-    ],
-    chdir = package_name(),
-    data = ensure_local_package_deps(TEST_DEPS) + TEST_FILES + APPLICATION_ASSETS + [
-        "//adev/tools:windows-chromium-path",
-        "@npm//@angular/build-tooling/bazel/browsers/chromium",
-    ],
-    env = {
-        "CHROME_BIN": "../$(CHROMIUM)",
-    },
-    toolchains = [
-        "@npm//@angular/build-tooling/bazel/browsers/chromium:toolchain_alias",
-    ],
-)

adev/README.md

@@ -1,53 +0,0 @@
-# [Angular.dev](https://www.angular.dev)
-
-This site is built with Angular.
-
-The content is written primarily in Markdown format located in `src/content`. For simple edits, you can directly edit the file on GitHub and generate a Pull Request.
-
-## Local Development
-
-For local development, [yarn](https://yarnpkg.com/) is the preferred package manager. You can setup a local environment with the following commands
-:
-
-```bash
-# Clone Angular repo
-git clone https://github.com/angular/angular.git
-
-# Navigate to project directory
-cd angular
-
-# Install dependencies
-yarn
-
-# Build and run local dev server
-# Note: Initial build will take some time
-yarn docs
-```
-
-If you are having issues with the docs building, see the [FAQs](#faqs) section.
-
-## Contributing
-
-Want to report a bug, contribute some code, or improve the documentation? Excellent!
-
-Read through our [contributing guidelines](/CONTRIBUTING.md) to learn about our submission process, coding rules, and more.
-
-And if you're new, check out one of our issues labeled as <kbd>[help wanted](https://github.com/angular/angular/labels/help%20wanted)</kbd> or <kbd>[good first issue](https://github.com/angular/angular/labels/good%20first%20issue)</kbd>.
-
-### Code of Conduct
-
-Help us keep Angular open and inclusive. Please read and follow our [Code of Conduct](CODE_OF_CONDUCT.md).
-
-## FAQs
-
-### The build is failing and I'm seeing `bazel:bazel failed: missing input file` messages.
-
-This is most likely due to a bazel dependency / caching issue. To resolve this, run the following command:
-
-```
-# Try this first
-yarn bazel clean
-
-# If that doesn't work, try it with the expunge flag
-yarn bazel clean --expunge
-```

adev/angular.json

@@ -1,109 +0,0 @@
-{
-  "$schema": "../node_modules/@angular/cli/lib/config/schema.json",
-  "version": 1,
-  "newProjectRoot": ".",
-  "projects": {
-    "angular-dev": {
-      "projectType": "application",
-      "schematics": {
-        "@schematics/angular:component": {
-          "style": "scss",
-          "standalone": true,
-          "changeDetection": "OnPush"
-        }
-      },
-      "root": ".",
-      "sourceRoot": "src",
-      "prefix": "adev",
-      "architect": {
-        "build": {
-          "builder": "@angular/build:application",
-          "options": {
-            "externalDependencies": ["path"],
-            "define": {
-              // We need this until xterm 5.6.0 is released
-              // see https://github.com/xtermjs/xterm.js/pull/4940
-              "self": "this"
-            },
-            "outputPath": "dist/angular-dev",
-            "index": "src/index.html",
-            "browser": "src/main.ts",
-            "server": "src/main.server.ts",
-            "ssr": true,
-            "polyfills": [],
-            "tsConfig": "tsconfig.app.json",
-            "inlineStyleLanguage": "scss",
-            "assets": ["src/favicon.ico", "src/robots.txt", "src/assets"],
-            "styles": ["@angular/docs/styles/global-styles.scss", "./src/local-styles.scss"],
-            "scripts": [],
-            "webWorkerTsConfig": "tsconfig.worker.json",
-            "optimization": {
-              "fonts": {
-                // TODO(josephperrott): enabled inline scripts
-                "inline": false
-              }
-            }
-          },
-          "configurations": {
-            "production": {
-              "outputHashing": "all"
-            },
-            "development": {
-              "optimization": false,
-              "extractLicenses": false,
-              "sourceMap": true
-            }
-          },
-          "defaultConfiguration": "production"
-        },
-        "serve": {
-          "builder": "@angular-devkit/build-angular:dev-server",
-          "configurations": {
-            "production": {
-              "buildTarget": "angular-dev:build:production"
-            },
-            "development": {
-              "buildTarget": "angular-dev:build:development"
-            }
-          },
-          "defaultConfiguration": "development",
-          "options": {
-            "buildTarget": "web-ui:build",
-            "headers": {
-              "Cross-Origin-Opener-Policy": "same-origin",
-              "Cross-Origin-Embedder-Policy": "require-corp"
-            }
-          }
-        },
-        "extract-i18n": {
-          "builder": "@angular-devkit/build-angular:extract-i18n",
-          "options": {
-            "buildTarget": "angular-dev:build"
-          }
-        },
-        "test": {
-          "builder": "@angular-devkit/build-angular:karma",
-          "options": {
-            "tsConfig": "tsconfig.spec.json",
-            "include": ["src/app"],
-            "karmaConfig": "karma.conf.js",
-            "main": "test-main.ts",
-            "inlineStyleLanguage": "scss",
-            "assets": ["src/favicon.ico", "src/assets"],
-            "styles": ["@angular/docs/styles/global-styles.scss"],
-            "scripts": [],
-            "webWorkerTsConfig": "tsconfig.worker.json"
-          }
-        }
-      }
-    }
-  },
-  "cli": {
-    "analytics": "dca119a9-da31-47f7-a6cb-b60541037021",
-    "cache": {
-      // Disable build caching as the cache folder will just be dropped
-      // when run under Bazel sandboxed execution.
-      "enabled": false
-    }
-  }
-}

adev/firebase.json

@@ -1,73 +0,0 @@
-{
-  "hosting": {
-    "target": "angular-docs",
-    "public": "./build/browser",
-    "ignore": ["**/.*"],
-    "headers": [
-      {
-        "source": "assets/images/tutorials/common/*.jpg",
-        "headers": [
-          {
-            "key": "Cross-Origin-Resource-Policy",
-            "value": "cross-origin"
-          },
-          {
-            "key": "Access-Control-Allow-Origin",
-            "value": "*"
-          }
-        ]
-      },
-      {
-        "source": "*.[0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f].+(css|js)",
-        "headers": [
-          {
-            "key": "Cache-Control",
-            "value": "public,max-age=31536000,immutable"
-          },
-          {
-            "key": "Access-Control-Allow-Origin",
-            "value": "*"
-          }
-        ]
-      },
-      {
-        "source": "/[0-9a-f][0-9a-f][0-9a-f].[0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f].js",
-        "headers": [
-          {
-            "key": "Cross-Origin-Embedder-Policy",
-            "value": "require-corp"
-          }
-        ]
-      },
-      {
-        "source": "/@(ngsw-worker.js|ngsw.json)",
-        "headers": [
-          {
-            "key": "Cache-Control",
-            "value": "no-cache"
-          }
-        ]
-      },
-      {
-        "source": "/**",
-        "headers": [
-          {
-            "key": "Cross-Origin-Opener-Policy",
-            "value": "same-origin"
-          },
-
-          {
-            "key": "Cross-Origin-Embedder-Policy",
-            "value": "require-corp"
-          }
-        ]
-      }
-    ],
-    "rewrites": [
-      {
-        "source": "**",
-        "destination": "/index.html"
-      }
-    ]
-  }
-}

adev/karma.conf.js

@@ -1,78 +0,0 @@
-// Karma configuration file, see link for more information
-// https://karma-runner.github.io/1.0/config/configuration-file.html
-
-const {getAdjustedChromeBinPathForWindows} = require('../adev/tools/windows-chromium-path');
-
-process.env.CHROME_BIN = getAdjustedChromeBinPathForWindows();
-
-module.exports = function (config) {
-  config.set({
-    basePath: '',
-    frameworks: ['jasmine', '@angular-devkit/build-angular'],
-    plugins: [
-      require('karma-jasmine'),
-      require('karma-chrome-launcher'),
-      require('karma-jasmine-html-reporter'),
-      require('karma-coverage'),
-      require('@angular-devkit/build-angular/plugins/karma'),
-      {'reporter:jasmine-seed': ['type', JasmineSeedReporter]},
-    ],
-    proxies: {
-      '/dummy/image': 'src/assets/images/logos/angular/angular.png',
-    },
-    client: {
-      clearContext: false, // leave Jasmine Spec Runner output visible in browser
-      jasmine: {
-        // you can add configuration options for Jasmine here
-        // the possible options are listed at https://jasmine.github.io/api/edge/Configuration.html
-        // for example, you can disable the random execution with `random: false`
-        // or set a specific seed with `seed: 4321`
-        random: true,
-        seed: '',
-      },
-    },
-    jasmineHtmlReporter: {
-      suppressAll: true, // removes the duplicated traces
-    },
-    coverageReporter: {
-      dir: require('path').join(__dirname, './coverage/site'),
-      subdir: '.',
-      reporters: [{type: 'html'}, {type: 'text-summary'}],
-    },
-    reporters: ['progress', 'kjhtml', 'jasmine-seed'],
-    port: 9876,
-    colors: true,
-    logLevel: config.LOG_INFO,
-    autoWatch: true,
-    customLaunchers: {
-      ChromeHeadlessNoSandbox: {
-        base: 'ChromeHeadless',
-        // See /integration/README.md#browser-tests for more info on these args
-        flags: [
-          '--no-sandbox',
-          '--headless',
-          '--disable-gpu',
-          '--disable-dev-shm-usage',
-          '--hide-scrollbars',
-          '--mute-audio',
-        ],
-      },
-    },
-    browsers: ['ChromeHeadlessNoSandbox'],
-    browserNoActivityTimeout: 60000,
-    singleRun: false,
-    restartOnFileChange: true,
-  });
-};
-
-// Helpers
-function JasmineSeedReporter(baseReporterDecorator) {
-  baseReporterDecorator(this);
-
-  this.onBrowserComplete = (browser, result) => {
-    const seed = result.order && result.order.random && result.order.seed;
-    if (seed) this.write(`${browser}: Randomized with seed ${seed}.\n`);
-  };
-
-  this.onRunComplete = () => undefined;
-}

adev/scripts/update-cli-help/README.md

@@ -1,3 +0,0 @@
-# Generating data for `angular.dev/cli`
-
-This script updates the Angular CLI help JSON files stored in `adev/src/content/cli/help`. This files are used to generate the [angular.dev CLI](https://angular.dev/cli) pages.

adev/scripts/update-cli-help/index.mjs

@@ -1,154 +0,0 @@
-import {execSync} from 'node:child_process';
-import {readFile, writeFile, readdir, mkdtemp, realpath, copyFile, unlink} from 'node:fs/promises';
-import {tmpdir} from 'node:os';
-import {get} from 'node:https';
-import {dirname, resolve as resolvePath, posix, join} from 'node:path';
-import {fileURLToPath} from 'node:url';
-import {existsSync, constants as fsConstants} from 'node:fs';
-
-const GITHUB_API = 'https://api.github.com/repos/';
-const CLI_BUILDS_REPO = 'angular/cli-builds';
-const GITHUB_API_CLI_BUILDS = posix.join(GITHUB_API, CLI_BUILDS_REPO);
-
-const scriptDir = dirname(fileURLToPath(import.meta.url));
-const CLI_HELP_CONTENT_PATH = resolvePath(scriptDir, '../../src/content/cli/help');
-const CLI_SHA_PATH = join(CLI_HELP_CONTENT_PATH, 'build-info.json');
-
-async function main() {
-  if (!existsSync(CLI_SHA_PATH)) {
-    throw new Error(`${CLI_SHA_PATH} does not exist.`);
-  }
-
-  const branch = process.env.GITHUB_REF;
-  const {sha: currentSha} = JSON.parse(await readFile(CLI_SHA_PATH, 'utf-8'));
-  const latestSha = await getShaFromCliBuilds(branch);
-
-  console.log(`Comparing ${currentSha}...${latestSha}.`);
-  const affectedFiles = await getAffectedFiles(currentSha, latestSha);
-  const changedHelpFiles = affectedFiles.filter((file) => file.startsWith('help/'));
-
-  if (changedHelpFiles.length === 0) {
-    console.log(`No 'help/**' files changed between ${currentSha} and ${latestSha}.`);
-
-    return;
-  }
-
-  console.log(
-    `The below help files changed between ${currentSha} and ${latestSha}:\n` +
-      changedHelpFiles.map((f) => '* ' + f).join('\n'),
-  );
-
-  const temporaryDir = await realpath(await mkdtemp(join(tmpdir(), 'cli-src-')));
-  const execOptions = {cwd: temporaryDir, stdio: 'inherit'};
-  execSync('git init', execOptions);
-  execSync('git remote add origin https://github.com/angular/cli-builds.git', execOptions);
-  // fetch a commit
-  execSync(`git fetch origin ${latestSha}`, execOptions);
-  // reset this repository's main branch to the commit of interest
-  execSync('git reset --hard FETCH_HEAD', execOptions);
-  // get sha when files where changed
-  const shaWhenFilesChanged = execSync(`git rev-list -1 ${latestSha} "help/"`, {
-    encoding: 'utf8',
-    cwd: temporaryDir,
-    stdio: ['ignore', 'pipe', 'ignore'],
-  }).trim();
-
-  // Delete existing JSON help files.
-  const helpFilesUnlink = (await readdir(CLI_HELP_CONTENT_PATH))
-    .filter((f) => f.endsWith('.json'))
-    .map((f) => unlink(join(CLI_HELP_CONTENT_PATH, f)));
-
-  await Promise.allSettled(helpFilesUnlink);
-
-  // Copy new help files
-  const tempHelpDir = join(temporaryDir, 'help');
-  const helpFilesCopy = (await readdir(tempHelpDir)).map((f) => {
-    const src = join(tempHelpDir, f);
-    const dest = join(CLI_HELP_CONTENT_PATH, f);
-
-    return copyFile(src, dest, fsConstants.COPYFILE_FICLONE);
-  });
-
-  await Promise.allSettled(helpFilesCopy);
-
-  // Write SHA to file.
-  await writeFile(
-    CLI_SHA_PATH,
-    JSON.stringify(
-      {
-        branchName: branch,
-        sha: shaWhenFilesChanged,
-      },
-      undefined,
-      2,
-    ),
-  );
-
-  console.log('\nChanges: ');
-  execSync(`git status --porcelain`, {stdio: 'inherit'});
-
-  console.log(`Successfully updated help files in '${CLI_HELP_CONTENT_PATH}'.\n`);
-}
-
-/**
- * Get SHA of a branch.
- *
- * @param {string} branch
- * @param {string} headSha
- * @returns Promise<string>
- */
-async function getShaFromCliBuilds(branch) {
-  const sha = await httpGet(`${GITHUB_API_CLI_BUILDS}/commits/${branch}`, {
-    headers: {Accept: 'application/vnd.github.VERSION.sha'},
-  });
-
-  if (!sha) {
-    throw new Error(`Unable to extract the SHA for '${branch}'.`);
-  }
-
-  return sha;
-}
-
-/**
- * Get the affected files.
- *
- * @param {string} baseSha
- * @param {string} headSha
- * @returns Promise<string[]>
- */
-async function getAffectedFiles(baseSha, headSha) {
-  const {files} = JSON.parse(
-    await httpGet(`${GITHUB_API_CLI_BUILDS}/compare/${baseSha}...${headSha}`),
-  );
-  return files.map((f) => f.filename);
-}
-
-function httpGet(url, options = {}) {
-  options.headers ??= {};
-  options.headers[
-    'Authorization'
-  ] = `token ${process.env.ANGULAR_CLI_BUILDS_READONLY_GITHUB_TOKEN}`;
-  // User agent is required
-  // https://docs.github.com/en/rest/overview/resources-in-the-rest-api?apiVersion=2022-11-28#user-agent-required
-  options.headers['User-Agent'] = `ADEV_Angular_CLI_Sources_Update`;
-
-  return new Promise((resolve, reject) => {
-    get(url, options, (res) => {
-      let data = '';
-      res
-        .on('data', (chunk) => {
-          data += chunk;
-        })
-        .on('end', () => {
-          resolve(data);
-        });
-    }).on('error', (e) => {
-      reject(e);
-    });
-  });
-}
-
-main().catch((err) => {
-  console.error(err);
-  process.exit(1);
-});

adev/shared-docs/BUILD.bazel

@@ -1,49 +0,0 @@
-load("//tools:defaults.bzl", "ng_module", "ng_package")
-
-package(default_visibility = ["//visibility:private"])
-
-ng_module(
-    name = "docs",
-    srcs = [
-        "index.ts",
-    ],
-    module_name = "@angular/docs",
-    deps = [
-        "//adev/shared-docs/components",
-        "//adev/shared-docs/constants",
-        "//adev/shared-docs/directives",
-        "//adev/shared-docs/interfaces",
-        "//adev/shared-docs/pipes",
-        "//adev/shared-docs/providers",
-        "//adev/shared-docs/services",
-        "//adev/shared-docs/testing",
-        "//adev/shared-docs/utils",
-    ],
-)
-
-ng_package(
-    name = "npm_package",
-    srcs = [
-        "package.json",
-        "//adev/shared-docs/icons",
-        "//adev/shared-docs/pipeline:BUILD.bazel",
-        "//adev/shared-docs/pipeline:_guides.bzl",
-        "//adev/shared-docs/pipeline:_playground.bzl",
-        "//adev/shared-docs/pipeline:_stackblitz.bzl",
-        "//adev/shared-docs/pipeline:_tutorial.bzl",
-        "//adev/shared-docs/pipeline:guides.mjs",
-        "//adev/shared-docs/pipeline:guides-no-mermaid.mjs",
-        "//adev/shared-docs/pipeline:playground.mjs",
-        "//adev/shared-docs/pipeline:stackblitz.mjs",
-        "//adev/shared-docs/pipeline:tutorial.mjs",
-        "//adev/shared-docs/pipeline/examples/template:files",
-        "//adev/shared-docs/pipeline/tutorials/common:files",
-        "//adev/shared-docs/styles",
-    ],
-    visibility = [
-        "//adev:__pkg__",
-    ],
-    deps = [
-        ":docs",
-    ],
-)

adev/shared-docs/components/BUILD.bazel

@@ -1,28 +0,0 @@
-load("//tools:defaults.bzl", "ts_library")
-
-package(default_visibility = ["//visibility:private"])
-
-ts_library(
-    name = "components",
-    srcs = [
-        "index.ts",
-    ],
-    visibility = [
-        "//adev/shared-docs:__pkg__",
-    ],
-    deps = [
-        "//adev/shared-docs/components/algolia-icon",
-        "//adev/shared-docs/components/breadcrumb",
-        "//adev/shared-docs/components/cookie-popup",
-        "//adev/shared-docs/components/copy-source-code-button",
-        "//adev/shared-docs/components/icon",
-        "//adev/shared-docs/components/navigation-list",
-        "//adev/shared-docs/components/search-dialog",
-        "//adev/shared-docs/components/select",
-        "//adev/shared-docs/components/slide-toggle",
-        "//adev/shared-docs/components/table-of-contents",
-        "//adev/shared-docs/components/text-field",
-        "//adev/shared-docs/components/top-level-banner",
-        "//adev/shared-docs/components/viewers",
-    ],
-)