pax_global_header00006660000000000000000000000064136210602620014510gustar00rootroot0000000000000052 comment=99e5e30c3a16a2fb080a4558b537c125d5ab4193 angular-cli-9.0.2/000077500000000000000000000000001362106026200137165ustar00rootroot00000000000000angular-cli-9.0.2/.bazelignore000066400000000000000000000000271362106026200162170ustar00rootroot00000000000000.git dist node_modules angular-cli-9.0.2/.bazelrc000066400000000000000000000133131362106026200153420ustar00rootroot00000000000000# Make TypeScript compilation fast, by keeping a few copies of the compiler # running as daemons, and cache SourceFile AST's to reduce parse time. build --strategy=TypeScriptCompile=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 saw a problem where VSCode traversed 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/ # Disable watchfs as it causes tests to be flaky on Windows # https://github.com/angular/angular/issues/29541 build --nowatchfs # Turn off legacy 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 ############################### # Saucelabs support # # Turn on these settings with # # --config=saucelabs # ############################### # Expose SauceLabs environment to actions # These environment variables are needed by # web_test_karma to run on Saucelabs test:saucelabs --action_env=SAUCE_USERNAME test:saucelabs --action_env=SAUCE_ACCESS_KEY test:saucelabs --action_env=SAUCE_READY_FILE test:saucelabs --action_env=SAUCE_PID_FILE test:saucelabs --action_env=SAUCE_TUNNEL_IDENTIFIER test:saucelabs --define=KARMA_WEB_TEST_MODE=SL_REQUIRED ############################### # 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="node ./tools/bazel_stamp_vars.js" ############################### # Output # ############################### # A more useful default output mode for bazel query # Prints eg. "ng_module rule //foo:bar" rather than just "//foo:bar" query --output=label_kind # By default, failing tests don't print any output, it goes to the log file test --test_output=errors ################################ # Settings for CircleCI # ################################ # Bazel flags for CircleCI are in /.circleci/bazel.rc ################################ # Remote Execution Setup # ################################ # Use the Angular team internal GCP instance for remote execution. build:remote --remote_instance_name=projects/internal-200822/instances/default_instance build:remote --project_id=internal-200822 # Starting with Bazel 0.27.0 strategies do not need to be explicitly # defined. See https://github.com/bazelbuild/bazel/issues/7480 build:remote --define=EXECUTOR=remote # Setup the remote build execution servers. build:remote --remote_cache=remotebuildexecution.googleapis.com build:remote --remote_executor=remotebuildexecution.googleapis.com build:remote --tls_enabled=true build:remote --auth_enabled=true build:remote --remote_timeout=3600 build:remote --jobs=50 # Setup the toolchain and platform for the remote build execution. The platform # is automatically configured by the "rbe_autoconfig" rule in the project workpsace. build:remote --host_javabase=@rbe_ubuntu1604_angular//java:jdk build:remote --javabase=@rbe_ubuntu1604_angular//java:jdk build:remote --host_java_toolchain=@bazel_tools//tools/jdk:toolchain_hostjdk8 build:remote --java_toolchain=@bazel_tools//tools/jdk:toolchain_hostjdk8 build:remote --crosstool_top=@rbe_ubuntu1604_angular//cc:toolchain build:remote --action_env=BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1 build:remote --extra_toolchains=@rbe_ubuntu1604_angular//config:cc-toolchain build:remote --extra_execution_platforms=//tools:rbe_ubuntu1604-angular build:remote --host_platform=//tools:rbe_ubuntu1604-angular build:remote --platforms=//tools:rbe_ubuntu1604-angular # Setup Build Event Service build:remote --bes_backend=buildeventservice.googleapis.com build:remote --bes_timeout=30s build:remote --bes_results_url="https://source.cloud.google.com/results/invocations/" # Set remote caching settings build:remote --remote_accept_cached=true ############################### # NodeJS rules settings # These settings are required for rules_nodejs ############################### # Turn on managed directories feature in Bazel # This allows us to avoid installing a second copy of node_modules common --experimental_allow_incremental_repository_updates #################################################### # 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 .bazelrc.userangular-cli-9.0.2/.circleci/000077500000000000000000000000001362106026200155515ustar00rootroot00000000000000angular-cli-9.0.2/.circleci/bazel.rc000066400000000000000000000014221362106026200171730ustar00rootroot00000000000000# 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. # Echo all the configuration settings and their source build --announce_rc # Don't be spammy in the logs build --noshow_progress # Don't run manual tests test --test_tag_filters=-manual # 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 "medium" class which is the default: # https://circleci.com/docs/2.0/configuration-reference/#resource_class build --local_resources=3072,2.0,1.0 # More details on failures build --verbose_failures=true # Retry in the event of flakes test --flaky_test_attempts=2 angular-cli-9.0.2/.circleci/config.yml000066400000000000000000000360551362106026200175520ustar00rootroot00000000000000# Configuration file for https://circleci.com/gh/angular/angular-cli # 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/ version: 2.1 # Variables ## IMPORTANT # If you change the cache key prefix, also sync the fallback_cache_key fallback to match. # Keep the static part of the cache key as prefix to enable correct fallbacks. # Windows needs its own cache key because binaries in node_modules are different. # See https://circleci.com/docs/2.0/caching/#restoring-cache for how prefixes work in CircleCI. var_1: &cache_key angular_devkit-0.11.0-{{ checksum "yarn.lock" }} var_2: &cache_key_fallback angular_devkit-0.11.0 var_1_win: &cache_key_win angular_devkit-win-0.11.0-{{ checksum "yarn.lock" }} var_2_win: &cache_key_fallback_win angular_devkit-win-0.11.0 var_3: &default_nodeversion "12.9" # Workspace initially persisted by the `setup` job, and then enhanced by `setup-and-build-win`. # https://circleci.com/docs/2.0/workflows/#using-workspaces-to-share-data-among-jobs # https://circleci.com/blog/deep-diving-into-circleci-workspaces/ var_4: &workspace_location . # Filter to ignore pull requests on a given job. var_5: &ignore_pull_requests filters: branches: ignore: - /pull\/.*/ # Executor Definitions # https://circleci.com/docs/2.0/reusing-config/#authoring-reusable-executors executors: action-executor: parameters: nodeversion: type: string default: *default_nodeversion docker: - image: circleci/node:<< parameters.nodeversion >> working_directory: ~/ng resource_class: small test-executor: parameters: nodeversion: type: string default: *default_nodeversion docker: - image: circleci/node:<< parameters.nodeversion >>-browsers working_directory: ~/ng environment: NPM_CONFIG_PREFIX: ~/.npm-global resource_class: large windows-executor: # Same as https://circleci.com/orbs/registry/orb/circleci/windows, but named. working_directory: ~/ng resource_class: windows.medium shell: powershell.exe -ExecutionPolicy Bypass machine: # Contents of this image: # https://circleci.com/docs/2.0/hello-world-windows/#software-pre-installed-in-the-windows-image image: windows-server-2019-vs2019:stable # Command Definitions # https://circleci.com/docs/2.0/reusing-config/#authoring-reusable-commands commands: custom_attach_workspace: description: Attach workspace at a predefined location steps: - attach_workspace: at: *workspace_location setup_windows: steps: - run: nvm install 12.1.0 - run: nvm use 12.1.0 - run: npm install -g yarn@1.17.3 - run: node --version - run: yarn --version setup_bazel_rbe: parameters: key: type: env_var_name default: CIRCLE_PROJECT_REPONAME steps: - run: name: "Setup bazel RBE remote execution" command: | touch .bazelrc.user; # We need ensure that the same default digest is used for encoding and decoding # with openssl. Openssl versions might have different default digests which can # cause decryption failures based on the openssl version. https://stackoverflow.com/a/39641378/4317734 openssl aes-256-cbc -d -in .circleci/gcp_token -md md5 -k "${<< parameters.key >>}" -out /home/circleci/.gcp_credentials; sudo bash -c "echo -e 'build --google_credentials=/home/circleci/.gcp_credentials' >> .bazelrc.user"; # Upload/don't upload local results to cache based on environment if [[ -n "{$CIRCLE_PR_NUMBER}" ]]; then sudo bash -c "echo -e 'build:remote --remote_upload_local_results=false\n' >> .bazelrc.user"; echo "Not uploading local build results to remote cache."; else sudo bash -c "echo -e 'build:remote --remote_upload_local_results=true\n' >> .bazelrc.user"; echo "Uploading local build results to remote cache."; fi # Enable remote builds sudo bash -c "echo -e 'build --config=remote' >> .bazelrc.user"; echo "Reading from remote cache for bazel remote jobs."; # Job definitions jobs: setup: executor: action-executor resource_class: medium steps: - checkout - run: name: Rebase PR on target branch command: > if [[ -n "${CIRCLE_PR_NUMBER}" ]]; then # User is required for rebase. git config user.name "angular-ci" git config user.email "angular-ci" # Rebase PR on top of target branch. node tools/rebase-pr.js angular/angular-cli ${CIRCLE_PR_NUMBER} else echo "This build is not over a PR, nothing to do." fi - restore_cache: keys: - *cache_key - *cache_key_fallback - run: yarn install --frozen-lockfile - persist_to_workspace: root: *workspace_location paths: - ./* - save_cache: key: *cache_key paths: - ~/.cache/yarn lint: executor: action-executor steps: - custom_attach_workspace - run: yarn lint - run: 'yarn bazel:format -mode=check || (echo "BUILD files not formatted. Please run ''yarn bazel:format''" ; exit 1)' # Run the skylark linter to check our Bazel rules - run: 'yarn bazel:lint || (echo -e "\n.bzl files have lint errors. Please run ''yarn bazel:lint-fix''"; exit 1)' validate: executor: action-executor steps: - custom_attach_workspace - run: yarn validate --ci test: executor: action-executor steps: - custom_attach_workspace - run: yarn test --full test-large: parameters: ve: type: boolean default: false glob: type: string default: "" executor: test-executor parallelism: 4 steps: - custom_attach_workspace - run: yarn webdriver-update - run: yarn test-large --full <<# parameters.ve >>--ve<> <<# parameters.glob >>--glob="<< parameters.glob >>"<> --nb-shards=${CIRCLE_NODE_TOTAL} --shard=${CIRCLE_NODE_INDEX} e2e-cli: parameters: ve: type: boolean default: false snapshots: type: boolean default: false executor: test-executor parallelism: 6 steps: - custom_attach_workspace - run: name: Initialize Environment command: ./.circleci/env.sh - run: name: Execute CLI E2E Tests command: PATH=~/.npm-global/bin:$PATH node ./tests/legacy-cli/run_e2e --nb-shards=${CIRCLE_NODE_TOTAL} --shard=${CIRCLE_NODE_INDEX} <<# parameters.ve >>--ve<> <<# parameters.snapshots >>--ng-snapshots<> e2e-cli-node-10: executor: name: test-executor nodeversion: "10.16" parallelism: 4 steps: - custom_attach_workspace - run: name: Initialize Environment command: | ./.circleci/env.sh # Ensure latest npm version to support local package repository PATH=~/.npm-global/bin:$PATH npm install --global npm - run: PATH=~/.npm-global/bin:$PATH node ./tests/legacy-cli/run_e2e --nb-shards=${CIRCLE_NODE_TOTAL} --shard=${CIRCLE_NODE_INDEX} test-browsers: executor: name: test-executor environment: E2E_BROWSERS: true resource_class: medium steps: - custom_attach_workspace - run: name: Initialize Environment command: ./.circleci/env.sh - run: name: Initialize Saucelabs command: setSecretVar SAUCE_ACCESS_KEY $(echo $SAUCE_ACCESS_KEY | rev) - run: name: Start Saucelabs Tunnel command: ./scripts/saucelabs/start-tunnel.sh background: true # Waits for the Saucelabs tunnel to be ready. This ensures that we don't run tests # too early without Saucelabs not being ready. - run: ./scripts/saucelabs/wait-for-tunnel.sh - run: PATH=~/.npm-global/bin:$PATH node ./tests/legacy-cli/run_e2e ./tests/legacy-cli/e2e/tests/misc/browsers.ts --ve - run: PATH=~/.npm-global/bin:$PATH node ./tests/legacy-cli/run_e2e ./tests/legacy-cli/e2e/tests/misc/browsers.ts - run: ./scripts/saucelabs/stop-tunnel.sh build: executor: action-executor steps: - custom_attach_workspace - run: yarn build # This is where we put all the misbehaving and flaky tests so we can fine-tune their conditions # and rerun them faster. flake-jail: executor: test-executor resource_class: medium steps: - custom_attach_workspace - run: yarn webdriver-update - run: yarn test-large --full --flakey --ve - run: yarn test-large --full --flakey build-bazel: executor: action-executor resource_class: large steps: - custom_attach_workspace - setup_bazel_rbe - run: sudo cp .circleci/bazel.rc /etc/bazel.bazelrc - run: yarn bazel:test snapshot_publish: executor: action-executor resource_class: medium steps: - custom_attach_workspace - run: name: Decrypt Credentials # Note: when changing the image, you might have to re-encrypt the credentials with a # matching version of openssl. # See https://stackoverflow.com/a/43847627/2116927 for more info. command: | openssl aes-256-cbc -d -in .circleci/github_token -k "${KEY}" -out ~/github_token -md md5 - run: name: Deployment to Snapshot command: | yarn admin snapshots --verbose --githubTokenFile=${HOME}/github_token publish: executor: action-executor steps: - custom_attach_workspace - run: name: Decrypt Credentials command: | openssl aes-256-cbc -d -in .circleci/npm_token -k "${KEY}" -out ~/.npmrc - run: name: Deployment to NPM command: | yarn admin publish --verbose # Windows jobs # CircleCI support for Windows jobs is still in preview. # Docs: https://github.com/CircleCI-Public/windows-preview-docs setup-and-build-win: executor: windows-executor steps: - custom_attach_workspace - setup_windows - restore_cache: keys: - *cache_key_win - *cache_key_fallback_win - run: yarn install --frozen-lockfile - run: yarn build - save_cache: key: *cache_key_win paths: # Get cache dir on windows via `yarn cache dir` - C:\Users\circleci\AppData\Local\Yarn\Cache\v4 # Only jobs downstream from this one will see the updated workspace # https://circleci.com/blog/deep-diving-into-circleci-workspaces/ - persist_to_workspace: root: *workspace_location paths: - ./* test-win: executor: windows-executor steps: - custom_attach_workspace - setup_windows - run: yarn test --full # Run partial e2e suite on PRs only. Master will run the full e2e suite with sharding. - run: if (Test-Path env:CIRCLE_PR_NUMBER) { node tests\legacy-cli\run_e2e.js "--glob=tests/{basic,ivy}/**" } e2e-cli-win: executor: windows-executor parallelism: 4 steps: - custom_attach_workspace - setup_windows - run: node tests\legacy-cli\run_e2e.js --nb-shards=$env:CIRCLE_NODE_TOTAL --shard=$env:CIRCLE_NODE_INDEX workflows: version: 2 default_workflow: jobs: # Linux jobs - setup - lint: requires: - setup - validate: requires: - setup - build: requires: - setup filters: branches: ignore: - /docs-preview/ - build-bazel: requires: - build - test: requires: - build - test-large: requires: - build - test-large: name: test-large-ve ve: true glob: "packages/angular_devkit/@(build_angular|build_ng_packagr)/@(src|test)/@(build|browser)/*_spec_large.ts" requires: - build - e2e-cli: post-steps: - store_artifacts: path: /tmp/dist destination: cli/new-production requires: - build - e2e-cli: name: e2e-cli-ve ve: true requires: - build - e2e-cli: name: e2e-cli-ng-snapshots snapshots: true requires: - e2e-cli pre-steps: - run: name: Don't run expensive e2e snapshots tests for forks other than renovate-bot and angular command: > if [[ "$CIRCLE_PR_USERNAME" != "renovate-bot" ]] && [[ "$CIRCLE_PROJECT_USERNAME" != "angular" || $CIRCLE_BRANCH != "master" ]]; then circleci step halt fi - e2e-cli: name: e2e-cli-ng-ve-snapshots snapshots: true ve: true requires: - e2e-cli pre-steps: - run: name: Don't run expensive e2e snapshots tests for forks other than renovate-bot and angular command: > if [[ "$CIRCLE_PR_USERNAME" != "renovate-bot" ]] && [[ "$CIRCLE_PROJECT_USERNAME" != "angular" || $CIRCLE_BRANCH != "master" ]]; then circleci step halt fi - e2e-cli-node-10: <<: *ignore_pull_requests requires: - e2e-cli - test-browsers: requires: - build - flake-jail: requires: - build # Windows jobs # These jobs only run after their non-windows counterparts finish successfully. # This isn't strictly necessary as there is no artifact dependency, but helps economize # CI resources by not attempting to build when we know it should fail. - setup-and-build-win: requires: # The Linux setup job also does checkout and rebase, which we get via the workspace. - setup - build - test-win: requires: - setup-and-build-win - test - e2e-cli-win: <<: *ignore_pull_requests requires: - setup-and-build-win - e2e-cli # Publish jobs - snapshot_publish: <<: *ignore_pull_requests requires: - test - build - e2e-cli - publish: requires: - test - build - e2e-cli - snapshot_publish filters: tags: only: /^v\d+/ branches: ignore: /.*/ angular-cli-9.0.2/.circleci/env-helpers.inc.sh000066400000000000000000000051561362106026200211140ustar00rootroot00000000000000#################################################################################################### # 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 ` 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 ` 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; echo "export $1=\"${2:-}\";" >> $BASH_ENV; # 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 computaions 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: # - ``: The name of the environment variable. The generated setter function will be # `setPublicVar_`. # - ``: 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 ` # # 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; } angular-cli-9.0.2/.circleci/env.sh000077500000000000000000000033611362106026200167030ustar00rootroot00000000000000#!/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 PROJECT_ROOT "$projectDir"; #################################################################################################### # Define SauceLabs environment variables for CircleCI. #################################################################################################### setPublicVar SAUCE_USERNAME "angular-tooling"; setSecretVar SAUCE_ACCESS_KEY "8c4ffce86ae6-c419-8ef4-0513-54267305"; 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-${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 # Source `$BASH_ENV` to make the variables available immediately. source $BASH_ENV; angular-cli-9.0.2/.circleci/gcp_token000066400000000000000000000044601362106026200174510ustar00rootroot00000000000000Salted__G0L¢Ñë]ÿ=RbÜc.±þ2å˜_Û#¦Äs«1öÊNwÝç>îáœþI»À’òå½ø„w*F­©Àtl œÙ×?µÀ/–”'‡b;„¢]€¯— lw³¡¬T•[&•‘@±r»óä^¨JD? kßxä-•”‹ *Øø|À8KÀœà…ÅRŒNj’L‡Å¦ÝÀ´ñ{ ýòžO[ÛVr¹›ìªµ—\ÿ(ÞDÂ89Ë©*ÅneeES$8¾ÝzNs»ÂU]:äþb7 ÑÆüp(aŠ¢'a í¶Ì³§‚H”û]e§Ø=©”˜†Ø}mGøBú.ÒÞ ²[t"/Z˜óçH¬Ñ·µWç€I jYÀ:2)³ÂÆúyÈÇØ´j[x²˜ÕeJáw<‚×Tå_Ííl^"÷›Á©Òf¬õç§utM­à˜ªqˆýA"FŸ·q¶ŽÖ€bf‰Y´oÐ \U‘¾´ÿ€JÛ(ÇÌ—Ö„T·sVÀ¾ ñ½<„»€èPkÜh–eö¿)ÁÔØ@®J¼Â(~¿F™]e¿èÛ®²jŤž4(mëœøsÓÊ·¤²ÏÝ*ä’d{8.{:Nha08æ88»ŸÝȤÊy›(¬¡‹ÜV†/¯€Jrw‹È·—¼ýø<ø×îVºßÄTÙFŸÆ¨H*ª4)mÙ³ìÉ v„l‡ú{ Ó9ÑmB‰-ÙSj,TGP½…LžÝÉ[8r<-^wÏç$r•Ây¤íXV댣€æA“ÉÕÐie€V¹qŒ¼Dt¼ú”Öù‚1Š)yô‘KyñA/’¡ˆúJݾ™ã¦"LxµÓ'¾±Ü|ézù#”¨È¹ž64#ê_O§íò­8¸¯Gî|àãÞÌLé"^Ž¹&º¤è‰¼Í½(Æxl3Ë= ìù“ ø«“”ÁÕ„¬f,iÊ`ÍMvå½äy2ÊÛË.k‰ÅˆþÔXsÕ¥BâTtˆÙØJ*( ÒÝñ£·¬ùÇí¬­ŽÓȨ«è.6[%K’r gë§PLM*”¿¸²ç€„ÑÕ¿IhébÅó›ÓÀŠ6O=k%ºmȯÄÏ%RxÒ()¬Z¬,*¹nU¸V/!ðþµ|ÁŽfXÔçãÿß„’HÅñ …ôäl)±æ>¤wö©¯0Xw8é±I]S±äç?–à=8õp6 ¤‹€Üßen¯aÄøˆ_¯¡£YäÜ:¶{S£» ²|VUÑÆ8Jzòå»»yўܥԇ·¹†Pôi}³]tŠ»ÊÍçÖg6’°-ý£)/"…;bFþ¯WÌ:ñÌ,6:ð=U¡pXm¼RÖ¤Å-?*œ± 1²åÎiŸ>ÆBO5QÞÆpܱ7MZ¶ŒåJýPx£ei™!gkŽNóö#¸RBòÑ¥pi‚‹‹‰Ä“KÁN×?/èÆ«¹5 Ÿ­½øj( eãï z6¾˜¬ÅED¦•²;Ù èJ¢u¸cßbÇLÈ@-nUÒŠh`Œ mO׉€úÌ‹¿N»¢$úôç~kßN·eÌ-±ñ-éêr%WaÓ97Óangular-cli-9.0.2/.circleci/github_token000066400000000000000000000001001362106026200201450ustar00rootroot00000000000000Salted__zÈùº¬ö"Bõ¾Y¾’|‚Û¢V”QÖ³UzWò±/G…îR ¡e}j‘% þÿ¦<%öáÉÿ–¼angular-cli-9.0.2/.circleci/npm_token000066400000000000000000000001401362106026200174610ustar00rootroot00000000000000Salted__°/¥ÙL Ž¡”ö¦°Â;ª…(.|©í¡ –ÚCŒàÔ’“þÖ5`h¢8Ðài8JÁo*´?}çû£3§0f´!Ð'ÛB¸Ì œ"UÆŠ&K!¨%Áɵڤangular-cli-9.0.2/.editorconfig000066400000000000000000000004061362106026200163730ustar00rootroot00000000000000# https://editorconfig.org root = true [*.ts] charset = utf-8 indent_style = space indent_size = 2 insert_final_newline = true spaces_around_brackets = inside trim_trailing_whitespace = true [*.md] insert_final_newline = false trim_trailing_whitespace = true angular-cli-9.0.2/.gitattributes000066400000000000000000000003441362106026200166120ustar00rootroot00000000000000# Auto detect text files and perform LF normalization * text=auto # JS and TS files must always use LF for tools to work *.js eol=lf *.ts eol=lf *.json eol=lf *.css eol=lf *.scss eol=lf *.less eol=lf *.html eol=lf *.svg eol=lf angular-cli-9.0.2/.github/000077500000000000000000000000001362106026200152565ustar00rootroot00000000000000angular-cli-9.0.2/.github/ISSUE_TEMPLATE.md000066400000000000000000000006121362106026200177620ustar00rootroot00000000000000🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑 Please help us process issues more efficiently by filing an issue using one of the following templates: https://github.com/angular/angular-cli/issues/new/choose Thank you! 🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑 angular-cli-9.0.2/.github/ISSUE_TEMPLATE/000077500000000000000000000000001362106026200174415ustar00rootroot00000000000000angular-cli-9.0.2/.github/ISSUE_TEMPLATE/1-bug-report.md000066400000000000000000000046741362106026200222220ustar00rootroot00000000000000--- name: "\U0001F41EBug report" about: Report a bug in Angular CLI --- # 🞠Bug report ### Command (mark with an `x`) ``` - [ ] new - [ ] build - [ ] serve - [ ] test - [ ] e2e - [ ] generate - [ ] add - [ ] update - [ ] lint - [ ] xi18n - [ ] run - [ ] config - [ ] help - [ ] version - [ ] doc ``` ### Is this a regression? Yes, the previous version in which this bug was not present was: .... ### Description A clear and concise description of the problem... ## 🔬 Minimal Reproduction ## 🔥 Exception or Error
## 🌠Your Environment
**Anything else relevant?** angular-cli-9.0.2/.github/ISSUE_TEMPLATE/2-feature-request.md000066400000000000000000000023301362106026200232410ustar00rootroot00000000000000--- name: "\U0001F680Feature request" about: Suggest a feature for Angular CLI --- # 🚀 Feature request ### Command (mark with an `x`) - [ ] new - [ ] build - [ ] serve - [ ] test - [ ] e2e - [ ] generate - [ ] add - [ ] update - [ ] lint - [ ] xi18n - [ ] run - [ ] config - [ ] help - [ ] version - [ ] doc ### Description A clear and concise description of the problem or missing capability... ### Describe the solution you'd like If you have a solution in mind, please describe it. ### Describe alternatives you've considered Have you considered any alternative solutions or workarounds? angular-cli-9.0.2/.github/ISSUE_TEMPLATE/3-docs-bug.md000066400000000000000000000010141362106026200216220ustar00rootroot00000000000000--- name: "📚 Docs or angular.io issue report" about: Report an issue in Angular's documentation or angular.io application --- 🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑 Please file any Docs or angular.io issues at: https://github.com/angular/angular/issues/new/choose For the time being, we keep Angular AIO issues in a separate repository. 🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑 angular-cli-9.0.2/.github/ISSUE_TEMPLATE/4-security-issue-disclosure.md000066400000000000000000000006721362106026200253000ustar00rootroot00000000000000--- name: âš ï¸Security issue disclosure about: Report a security issue in Angular Framework, Material, or CLI --- 🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑 Please read https://angular.io/guide/security#report-issues on how to disclose security related issues. 🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑 angular-cli-9.0.2/.github/ISSUE_TEMPLATE/5-support-request.md000066400000000000000000000010501362106026200233230ustar00rootroot00000000000000--- name: "â“Support request" about: Questions and requests for support --- 🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑 Please do not file questions or support requests on the GitHub issues tracker. You can get your questions answered using other communication channels. Please see: https://github.com/angular/angular-cli/blob/master/CONTRIBUTING.md#question Thank you! 🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑 angular-cli-9.0.2/.github/ISSUE_TEMPLATE/6-angular-framework.md000066400000000000000000000007441362106026200235570ustar00rootroot00000000000000--- name: "âš¡Angular Framework" about: Issues and feature requests for Angular Framework --- 🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑 Please file any Angular Framework issues at: https://github.com/angular/angular/issues/new/choose For the time being, we keep Angular issues in a separate repository. 🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑 angular-cli-9.0.2/.github/ISSUE_TEMPLATE/7-angular-material.md000066400000000000000000000007541362106026200233620ustar00rootroot00000000000000--- name: "\U0001F48EAngular Material" about: Issues and feature requests for Angular Material --- 🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑 Please file any Angular Material issues at: https://github.com/angular/material2/issues/new For the time being, we keep Angular Material issues in a separate repository. 🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑 angular-cli-9.0.2/.github/SAVED_REPLIES.md000066400000000000000000000140171362106026200176300ustar00rootroot00000000000000# Saved Responses for Angular CLI's Issue Tracker The following are canned responses that the Angular CLI team should use to close issues on our issue tracker that fall into the listed resolution categories. Since GitHub currently doesn't allow us to have a repository-wide or organization-wide list of [saved replies](https://help.github.com/articles/working-with-saved-replies/), these replies need to be maintained by individual team members. Since the responses can be modified in the future, all responses are versioned to simplify the process of keeping the responses up to date. ## Angular CLI: Already Fixed (v1) ``` Thanks for reporting this issue. Luckily, it has already been fixed in one of the recent releases. Please update to the most recent version to resolve the problem. If the problem persists in your application after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior. You can use `ng new repro-app` to create a new project where you reproduce the problem. ``` ## Angular CLI: Don't Understand (v1) ``` I'm sorry, but we don't understand the problem you are reporting. If the problem persists, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior. You can use `ng new repro-app` to create a new project where you reproduce the problem. ``` ## Angular CLI: Duplicate (v1.1) ``` Thanks for reporting this issue. However, this issue is a duplicate of #. Please subscribe to that issue for future updates. ``` ## Angular CLI: Insufficient Information Provided (v1) ``` Thanks for reporting this issue. However, you didn't provide sufficient information for us to understand and reproduce the problem. Please check out [our submission guidelines](https://github.com/angular/angular-cli/blob/master/CONTRIBUTING.md#-submitting-an-issue) to understand why we can't act on issues that are lacking important information. If the problem persists, please file a new issue and ensure you provide all of the required information when filling out the issue template. ``` ## Angular CLI: NPM install issue (v1) ``` This seems like a problem with your node/npm and not with Angular CLI. Please have a look at the [fixing npm permissions page](https://docs.npmjs.com/getting-started/fixing-npm-permissions), [common errors page](https://docs.npmjs.com/troubleshooting/common-errors), [npm issue tracker](https://github.com/npm/npm/issues), or open a new issue if the problem you are experiencing isn't known. ``` ## Angular CLI: Issue Outside of Angular CLI (v1.1) ``` I'm sorry, but this issue is not caused by Angular CLI. Please contact the author(s) of the project or file an issue on their issue tracker. ``` ## Angular CLI: Non-reproducible (v1) ``` I'm sorry, but we can't reproduce the problem following the instructions you provided. Remember that we have a large number of issues to resolve, and have only a limited amount of time to reproduce your issue. Short, explicit instructions make it much more likely we'll be able to reproduce the problem so we can fix it. If the problem persists, please open a new issue following [our submission guidelines](https://github.com/angular/angular-cli/blob/master/CONTRIBUTING.md#-submitting-an-issue). A good way to make a minimal repro is to create a new app via `ng new repro-app` and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here. ``` ## Angular CLI: Obsolete (v1) ``` Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular CLI version. If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior. ``` ## Angular CLI: Support Request (v1) ``` Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on [StackOverflow](http://stackoverflow.com/) using tag `angular-cli`. If you are wondering why we don't resolve support issues via the issue tracker, please [check out this explanation](https://github.com/angular/angular-cli/blob/master/CONTRIBUTING.md#-got-a-question-or-problem). ``` ## Angular CLI: Static Analysis errors (v1) ``` Hello, errors like `Error encountered resolving symbol values statically` mean that there has been some problem in statically analyzing your app. Angular CLI always runs *some* static analysis, even in JIT mode, in order to discover lazy-loaded routes. This may cause a lot of static analysis errors to surface when importing your project into the CLI, or upgrading for older versions where we didn't run this kind of analysis. Below are good resources on how to to debug these errors: - https://gist.github.com/chuckjaz/65dcc2fd5f4f5463e492ed0cb93bca60 - https://github.com/rangle/angular-2-aot-sandbox#aot-dos-and-donts If your problem still persists, it might be a bug with the Angular Compiler itself. In that case, please open an issue in https://github.com/angular/angular. ``` ## Angular CLI: Lockfiles (v1) ``` I'd like to remind everyone that **you only have reproducible installs if you use a lockfile**. Both [NPM v5+](https://docs.npmjs.com/files/package-locks) and [Yarn](https://yarnpkg.com/lang/en/docs/yarn-lock/) support lockfiles. If your CI works one day but not the next and you did not change your code or `package.json`, it is likely because one of your dependencies had a bad release and you did not have a lockfile. **It is your responsibility as a library consumer to use lockfiles**. No one wants to do a release with bugs but it sometimes happens, and the best we can do is to fix it as fast as possible with a new release. When you have a couple of thousand total dependencies it is only a matter of time until one of them has a bad release. ``` angular-cli-9.0.2/.github/_CODEOWNERS.tmp000066400000000000000000000020251362106026200176060ustar00rootroot00000000000000/packages/_/ @hansl @clydin /packages/angular/pwa @hansl @Brocco /packages/angular_devkit/architect/ @filipesilva @hansl /packages/angular_devkit/architect_cli/ @filipesilva @hansl /packages/angular_devkit/build_angular/ @filipesilva @clydin /packages/angular_devkit/build_ng_packagr/ @filipesilva @clydin /packages/angular_devkit/build_optimizer/ @filipesilva @clydin /packages/angular_devkit/core/ @hansl @clydin /packages/angular_devkit/schematics/ @hansl @Brocco /packages/angular_devkit/schematics_cli/ @hansl @Brocco /packages/ngtools/webpack/ @hansl @filipesilva @clydin /packages/schematics/angular/ @hansl @Brocco /packages/schematics/package_update/ @hansl @Brocco /packages/schematics/schematics/ @hansl @Brocco /packages/schematics/update/ @hansl @Brocco /rules/ @hansl @clydin /scripts/ @hansl @clydin angular-cli-9.0.2/.github/angular-robot.yml000066400000000000000000000070761362106026200205670ustar00rootroot00000000000000# Configuration for angular-robot # options for the merge plugin merge: # the status will be added to your pull requests status: # set to true to disable disabled: false # the name of the status context: "ci/angular: merge status" # text to show when all checks pass successText: "All checks passed!" # text to show when some checks are failing failureText: "The following checks are failing:" # 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!" # label to monitor mergeLabel: "PR action: merge" # list of checks that will determine if the merge label can be added checks: # whether the PR shouldn't have a conflict with the base branch noConflict: true # whether the PR should have all reviews completed. requireReviews: true # 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: - "PR target: *" - "cla: yes" # list of labels that a PR shouldn't have, checked after the required labels with a regexp forbiddenLabels: - "PR target: TBD" - "PR action: cleanup" - "PR action: review" - "PR state: blocked" - "cla: no" # list of PR statuses that need to be successful requiredStatuses: - "ci/circleci: build" - "ci/circleci: build-bazel" - "ci/circleci: setup" - "ci/circleci: setup-and-build-win" - "ci/circleci: lint" - "ci/circleci: validate" - "ci/circleci: test" - "ci/circleci: test-win" - "ci/circleci: test-large" - "ci/circleci: test-large-ve" - "ci/circleci: e2e-cli" - "ci/circleci: e2e-cli-ve" - "ci/circleci: test-browsers" - "ci/angular: size" - "cla/google" # 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 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: # set to true to disable disabled: false # number of the milestone to apply when the issue has not been triaged yet needsTriageMilestone: 11, # number of the milestone to apply when the issue is triaged defaultMilestone: 12, # arrays of labels that determine if an issue has been triaged by the caretaker l1TriageLabels: - - "comp: *" # arrays of labels that determine if an issue has been fully triaged l2TriageLabels: - - "type: bug/fix" - "severity*" - "freq*" - "comp: *" - - "type: feature" - "comp: *" - - "type: refactor" - "comp: *" - - "type: RFC / Discussion / question" - "comp: *" - - "type: docs" - "comp: *" # Size checking size: circleCiStatusName: "ci/circleci: e2e-cli" maxSizeIncrease: 10000 comment: false angular-cli-9.0.2/.github/workflows/000077500000000000000000000000001362106026200173135ustar00rootroot00000000000000angular-cli-9.0.2/.github/workflows/lock-closed.yml000066400000000000000000000004521362106026200222360ustar00rootroot00000000000000name: Lock Inactive Issues on: schedule: # Run at 08:00 every day - cron: '0 8 * * *' jobs: lock_closed: runs-on: ubuntu-latest steps: - uses: angular/dev-infra/github-actions/lock-closed@a4fd924 with: lock-bot-key: ${{ secrets.LOCK_BOT_PRIVATE_KEY }} angular-cli-9.0.2/.gitignore000066400000000000000000000003741362106026200157120ustar00rootroot00000000000000# Outputs bazel-* test-project-host-* dist/ dist-schema/ # IDEs .idea/ jsconfig.json .vscode/ # Typings file. typings/ # Misc coverage/ node_modules/ tmp/ npm-debug.log* yarn-error.log* .ng_pkg_build/ # Mac OSX Finder files. **/.DS_Store .DS_Store angular-cli-9.0.2/.mailmap000066400000000000000000000047501362106026200153450ustar00rootroot00000000000000# Please keep this file in alphabetical order, per section. ################################################################################ # Angular Team ################################################################################ Hans Larsen Igor Minar Igor Minar ################################################################################ # Angular CLI Team ################################################################################ Charles Lyding Charles Lyding <19598772+clydin@users.noreply.github.com> Filipe Silva Mike Brocchi Alan Agius Alan Agius ################################################################################ # OpenSource Contributors ################################################################################ Ashok Tamang Ashok Tamang Bram Borggreve Carlo Dapor Cédric Exbrayat Cédric Exbrayat Chris Pearce Chris Pearce Dominic Watson Dominic Watson Jeremy Wells Jan Kuri Jim Cummins Jim Cummins John Papa John Papa Meligy MichaÅ‚ GoÅ‚Ä™biowski-Owczarek Preston Van Loon Preston Van Loon Rodric Haddad Shai Reznik Shai Reznik Shai Reznik Stephen Cavaliere Stephen Cavaliere angular-cli-9.0.2/.monorepo.json000066400000000000000000000115111362106026200165240ustar00rootroot00000000000000{ "badges": [ [ { "image": "https://img.shields.io/circleci/project/github/angular/angular-cli/master.svg?label=circleci", "label": "CircleCI branch", "url": "https://circleci.com/gh/angular/angular-cli" }, { "title": "![Dependency Status](https://david-dm.org/angular/angular-cli.svg)", "url": "https://david-dm.org/angular/angular-cli" }, { "title": "![devDependency Status](https://david-dm.org/angular/angular-cli/dev-status.svg)", "url": "https://david-dm.org/angular/angular-cli?type=dev" } ], [ { "label": "License", "image": "https://img.shields.io/npm/l/@angular/cli.svg", "url": "/LICENSE" } ], [ { "label": "GitHub forks", "image": "https://img.shields.io/github/forks/angular/angular-cli.svg?style=social&label=Fork", "url": "https://github.com/angular/angular-cli/fork" }, { "label": "GitHub stars", "image": "https://img.shields.io/github/stars/angular/angular-cli.svg?style=social&label=Star", "url": "https://github.com/angular/angular-cli" } ] ], "links": { "Gitter": "https://gitter.im/angular/angular-cli", "Contributing": "/CONTRIBUTING.md", "Angular CLI": "http://github.com/angular/angular-cli" }, "packages": { "@_/benchmark": { }, "@_/builders": { }, "devkit": { }, "@angular/cli": { "name": "Angular CLI", "section": "Tooling", "links": [ { "label": "README", "url": "/packages/angular/cli/README.md" } ], "snapshotRepo": "angular/cli-builds" }, "@angular/pwa": { "name": "Angular PWA Schematics", "section": "Schematics", "snapshotRepo": "angular/angular-pwa-builds" }, "@angular-devkit/architect": { "name": "Architect", "links": [ { "label": "README", "url": "/packages/angular_devkit/architect/README.md" } ], "snapshotRepo": "angular/angular-devkit-architect-builds" }, "@angular-devkit/architect-cli": { "name": "Architect CLI", "section": "Tooling", "snapshotRepo": "angular/angular-devkit-architect-cli-builds" }, "@angular-devkit/benchmark": { "name": "Benchmark", "section": "Tooling" }, "@angular-devkit/build-optimizer": { "name": "Build Optimizer", "links": [ { "label": "README", "url": "/packages/angular_devkit/build_optimizer/README.md" } ], "snapshotRepo": "angular/angular-devkit-build-optimizer-builds" }, "@angular-devkit/build-ng-packagr": { "name": "Build NgPackagr", "links": [ { "label": "README", "url": "/packages/angular_devkit/build_ng_packagr/README.md" } ], "snapshotRepo": "angular/angular-devkit-build-ng-packagr-builds" }, "@angular-devkit/build-angular": { "name": "Build Angular", "links": [ { "label": "README", "url": "/packages/angular_devkit/build_angular/README.md" } ], "snapshotRepo": "angular/angular-devkit-build-angular-builds" }, "@angular-devkit/build-webpack": { "name": "Build Webpack", "links": [ { "label": "README", "url": "/packages/angular_devkit/build_webpack/README.md" } ], "snapshotRepo": "angular/angular-devkit-build-webpack-builds" }, "@angular-devkit/core": { "name": "Core", "links": [ { "label": "README", "url": "/packages/angular_devkit/core/README.md" } ], "snapshotRepo": "angular/angular-devkit-core-builds" }, "@angular-devkit/schematics": { "name": "Schematics", "links": [ { "label": "README", "url": "/packages/angular_devkit/schematics/README.md" } ], "snapshotRepo": "angular/angular-devkit-schematics-builds" }, "@angular-devkit/schematics-cli": { "name": "Schematics CLI", "section": "Tooling", "snapshotRepo": "angular/angular-devkit-schematics-cli-builds" }, "@ngtools/webpack": { "name": "Webpack Angular Plugin", "section": "Misc", "snapshotRepo": "angular/ngtools-webpack-builds" }, "@schematics/angular": { "name": "Angular Schematics", "section": "Schematics", "snapshotRepo": "angular/schematics-angular-builds" }, "@schematics/schematics": { "name": "Schematics Schematics", "section": "Schematics", "snapshotRepo": "angular/schematics-schematics-builds" }, "@schematics/update": { "name": "Package Update Schematics", "section": "Schematics", "snapshotRepo": "angular/schematics-update-builds" } } } angular-cli-9.0.2/.nvmrc000066400000000000000000000000031362106026200150350ustar00rootroot0000000000000010 angular-cli-9.0.2/.prettierignore000066400000000000000000000000111362106026200167510ustar00rootroot00000000000000/etc/api angular-cli-9.0.2/.prettierrc000066400000000000000000000001111362106026200160730ustar00rootroot00000000000000{ "printWidth": 100, "singleQuote": true, "trailingComma": "all" } angular-cli-9.0.2/BUILD000066400000000000000000000006201362106026200144760ustar00rootroot00000000000000# Copyright Google Inc. All Rights Reserved. # # Use of this source code is governed by an MIT-style license that can be # found in the LICENSE file at https://angular.io/license package(default_visibility = ["//visibility:public"]) licenses(["notice"]) exports_files([ "LICENSE", "tsconfig.json", # @external "tsconfig-test.json", # @external "tslint.base.json", # @external ]) angular-cli-9.0.2/CONTRIBUTING.md000066400000000000000000000312041362106026200161470ustar00rootroot00000000000000# Contributing to Angular DevKit We would love for you to contribute to DevKit 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) - [Issues and Bugs](#issue) - [Feature Requests](#feature) - [Submission Guidelines](#submit) - [Coding Rules](#rules) - [Commit Message Guidelines](#commit) - [Signing the CLA](#cla) - [Updating the Public API](#public-api) ## Code of Conduct Help us keep Angular open and inclusive. Please read and follow our [Code of Conduct][coc]. ## Got a Question or Problem? Please, do not open issues for the 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 [StackOverflow](https://stackoverflow.com/questions/tagged/angular-devkit) where the questions should be tagged with tag `angular-cli` or `angular-devkit`. StackOverflow is a much better place to ask questions since: - there are thousands of people willing to help on StackOverflow - questions and answers stay available for public viewing so your question / answer might help someone else - StackOverflow's voting system assures that the best answers are prominently visible. To save your and our time we will be systematically closing all the issues that are requests for general support and redirecting people to StackOverflow. If you would like to chat about the question in real-time, you can reach out via [our gitter channel][gitter]. ## Found an Issue? If you find a bug in the source code or a mistake in the documentation, 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. ## Want a Feature? You can *request* a new feature by [submitting an issue](#submit-issue) to our [GitHub Repository][github]. 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). ## Submission Guidelines ### Submitting an Issue 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. Having a reproducible scenario gives us wealth of important information without going back & forth to you with additional questions like: - version of Angular CLI used - `.angular-cli.json` or `angular.json` configuration - version of Angular DevKit used - 3rd-party libraries and their versions - and most importantly - a use-case that fails A minimal reproduce scenario using allows us to quickly confirm a bug (or point out coding problem) as well as confirm that we are fixing the right problem. 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 repository. 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. 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 don't have enough info to be reproduced. You can file new issues by selecting from our [new issue templates](https://github.com/angular/angular-cli/issues/new/choose) and filling out the issue template. ### Submitting a Pull Request (PR) Before you submit your Pull Request (PR) consider the following guidelines: * Search [GitHub](https://github.com/angular/angular-cli/pulls) for an open or closed PR that relates to your submission. You don't want to duplicate effort. * Please sign our [Contributor License Agreement (CLA)](#cla) before sending PRs. We cannot accept code without this. * Make your changes in a new git branch: ```shell git checkout -b my-fix-branch master ``` * Create your patch, **including appropriate test cases**. * Follow our [Coding Rules](#rules). * Run the full Angular CLI and DevKit test suite, as described in the [developer documentation][dev-doc], and ensure that all tests pass (coming soon). * 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 -a ``` Note: the optional commit `-a` command line option will automatically "add" and "rm" edited files. * Push your branch to GitHub: ```shell git push origin my-fix-branch ``` * In GitHub, send a pull request to `angular/angular-cli:master`. * If we suggest changes then: * Make the required updates. * Re-run the Angular DevKit 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 rebase master -i git push -f ``` That's it! Thank you for your contribution! #### 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: * Delete the remote branch on GitHub either through the GitHub web UI or your local shell as follows: ```shell git push origin --delete my-fix-branch ``` * Check out the master branch: ```shell git checkout master -f ``` * Delete the local branch: ```shell git branch -D my-fix-branch ``` * Update your master with the latest upstream version: ```shell git pull --ff upstream master ``` ## 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 or e2e-tests). * 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**. ## 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 DevKit change log**. ### 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**: ``` ():