pax_global_header00006660000000000000000000000064134065471720014523gustar00rootroot0000000000000052 comment=1c96c85f8051596790fee37defef05cc7ceec2e1 angular-cli-7.1.4/000077500000000000000000000000001340654717200137325ustar00rootroot00000000000000angular-cli-7.1.4/.appveyor.yml000066400000000000000000000012001340654717200163710ustar00rootroot00000000000000environment: nodejs_version: "10.9.0" # Same version as used in CircleCI. matrix: fast_finish: true skip_tags: true skip_branch_with_pr: true install: - ps: Install-Product node $env:nodejs_version # --network-timeout is a workaround for https://github.com/yarnpkg/yarn/issues/6221 - yarn --frozen-lockfile --network-timeout=500000 - yarn webdriver-update-appveyor test_script: - node --version - yarn --version - yarn test - node tests\legacy-cli\run_e2e.js --appveyor "--glob=tests/{basic,commands,generate,build/styles}/**" build: off deploy: off cache: - node_modules -> yarn.lock - "%LOCALAPPDATA%\\Yarn" angular-cli-7.1.4/.bazelignore000066400000000000000000000000221340654717200162260ustar00rootroot00000000000000dist node_modules angular-cli-7.1.4/.bazelrc000066400000000000000000000004231340654717200153540ustar00rootroot00000000000000# 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 # Performance: avoid stat'ing input files build --watchfs test --test_output=errors angular-cli-7.1.4/.circleci/000077500000000000000000000000001340654717200155655ustar00rootroot00000000000000angular-cli-7.1.4/.circleci/bazel.rc000066400000000000000000000013301340654717200172050ustar00rootroot00000000000000# 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 # Retry in the event of flakes test --flaky_test_attempts=2 angular-cli-7.1.4/.circleci/config.yml000066400000000000000000000132671340654717200175660ustar00rootroot00000000000000# 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/ # 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 angular_devkit-{{ checksum "yarn.lock" }}-0.7.0 var_3: &node_8_docker_image angular/ngcontainer:0.3.3 # Settings common to each job anchor_1: &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/${CI_PULL_REQUEST//*pull\//}/merge" anchor_3: &root_package_lock_key key: *cache_key anchor_4: &attach_options at: . # Job definitions version: 2 jobs: install: <<: *defaults steps: - checkout: *post_checkout - restore_cache: *root_package_lock_key - run: yarn install --frozen-lockfile - persist_to_workspace: root: . paths: - ./* - save_cache: <<: *root_package_lock_key paths: - ~/.cache/yarn lint: <<: *defaults steps: - attach_workspace: *attach_options - run: npm run lint validate: <<: *defaults steps: - attach_workspace: *attach_options - run: npm run validate -- --ci test: <<: *defaults steps: - attach_workspace: *attach_options - run: npm run test -- --full test-large: <<: *defaults resource_class: large parallelism: 4 steps: - attach_workspace: *attach_options - run: npm run webdriver-update-circleci - run: npm run test-large -- --full --nb-shards=${CIRCLE_NODE_TOTAL} --shard=${CIRCLE_NODE_INDEX} e2e-cli: <<: *defaults environment: BASH_ENV: ~/.profile resource_class: xlarge parallelism: 4 steps: - attach_workspace: *attach_options - run: xvfb-run -a node ./tests/legacy-cli/run_e2e --nb-shards=${CIRCLE_NODE_TOTAL} --shard=${CIRCLE_NODE_INDEX} - store_artifacts: path: /tmp/dist destination: cli/new-production e2e-node-8: <<: *defaults # Overwrite docker image to node 8. docker: - image: *node_8_docker_image environment: BASH_ENV: ~/.profile resource_class: xlarge parallelism: 2 steps: - attach_workspace: *attach_options - run: npm install --global npm@6 - run: xvfb-run -a node ./tests/legacy-cli/run_e2e --glob=tests/basic/* --nb-shards=${CIRCLE_NODE_TOTAL} --shard=${CIRCLE_NODE_INDEX} e2e-cli-ng-snapshots: <<: *defaults environment: BASH_ENV: ~/.profile resource_class: xlarge parallelism: 4 steps: - attach_workspace: *attach_options - run: xvfb-run -a node ./tests/legacy-cli/run_e2e --nb-shards=${CIRCLE_NODE_TOTAL} --shard=${CIRCLE_NODE_INDEX} --ng-snapshots build: <<: *defaults steps: - attach_workspace: *attach_options - run: npm run admin -- build build-bazel: <<: *defaults resource_class: xlarge steps: - attach_workspace: *attach_options - run: sudo cp .circleci/bazel.rc /etc/bazel.bazelrc - run: bazel test //packages/... snapshot_publish: <<: *defaults steps: - attach_workspace: *attach_options - run: name: Decrypt Credentials command: | openssl aes-256-cbc -d -in .circleci/github_token -k "${KEY}" -out ~/github_token - run: name: Deployment to Snapshot command: | npm run admin -- snapshots --verbose --githubTokenFile=${HOME}/github_token publish: <<: *defaults steps: - attach_workspace: *attach_options - run: name: Decrypt Credentials command: | openssl aes-256-cbc -d -in .circleci/npm_token -k "${KEY}" -out ~/.npmrc - run: name: Deployment to NPM command: | npm run admin -- publish --verbose workflows: version: 2 default_workflow: jobs: - install - lint: requires: - install - validate: requires: - install - build: requires: - install filters: branches: ignore: - /docs-preview/ - build-bazel: requires: - build - test: requires: - build - test-large: requires: - build - e2e-cli: requires: - build - e2e-node-8: requires: - build - snapshot_publish_docs: requires: - install filters: branches: only: - /docs-preview/ - e2e-cli-ng-snapshots: requires: - build filters: branches: only: master - snapshot_publish: requires: - test - build - e2e-cli filters: branches: ignore: - /pull\/.*/ - publish: requires: - test - build - e2e-cli - snapshot_publish filters: tags: only: /^v\d+/ branches: ignore: /.*/ angular-cli-7.1.4/.circleci/github_token000066400000000000000000000001001340654717200201610ustar00rootroot00000000000000Salted__zÈùº¬ö"Bõ¾Y¾’|‚Û¢V”QÖ³UzWò±/G…îR ¡e}j‘% þÿ¦<%öáÉÿ–¼angular-cli-7.1.4/.circleci/npm_token000066400000000000000000000001401340654717200174750ustar00rootroot00000000000000Salted__°/¥ÙL Ž¡”ö¦°Â;ª…(.|©í¡ –ÚCŒàÔ’“þÖ5`h¢8Ðài8JÁo*´?}çû£3§0f´!Ð'ÛB¸Ì œ"UÆŠ&K!¨%Áɵڤangular-cli-7.1.4/.editorconfig000066400000000000000000000004061340654717200164070ustar00rootroot00000000000000# 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-7.1.4/.gitattributes000066400000000000000000000003441340654717200166260ustar00rootroot00000000000000# 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-7.1.4/.github/000077500000000000000000000000001340654717200152725ustar00rootroot00000000000000angular-cli-7.1.4/.github/ISSUE_TEMPLATE.md000066400000000000000000000022071340654717200200000ustar00rootroot00000000000000 ### Bug Report or Feature Request (mark with an `x`) ``` - [ ] bug report -> please search issues before submitting - [ ] feature request ``` ### Command (mark with an `x`) ``` - [ ] new - [ ] build - [ ] serve - [ ] test - [ ] e2e - [ ] generate - [ ] add - [ ] update - [ ] lint - [ ] xi18n - [ ] run - [ ] config - [ ] help - [ ] version - [ ] doc ``` ### Versions ### Repro steps ### The log given by the failure ### Desired functionality ### Mention any other details that might be useful angular-cli-7.1.4/.github/SAVED_REPLIES.md000066400000000000000000000140171340654717200176440ustar00rootroot00000000000000# 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-7.1.4/.github/_CODEOWNERS.tmp000066400000000000000000000020251340654717200176220ustar00rootroot00000000000000/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-7.1.4/.github/angular-robot.yml000066400000000000000000000065461340654717200206040ustar00rootroot00000000000000# 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: - "continuous-integration/appveyor/pr" - "ci/circleci: build" - "ci/circleci: build-bazel" - "ci/circleci: install" - "ci/circleci: lint" - "ci/circleci: validate" - "ci/circleci: test" - "ci/circleci: test-large" # 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: true angular-cli-7.1.4/.gitignore000066400000000000000000000003741340654717200157260ustar00rootroot00000000000000# 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-7.1.4/.mailmap000066400000000000000000000045121340654717200153550ustar00rootroot00000000000000# 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 ################################################################################ # 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-7.1.4/.monorepo.json000066400000000000000000000143331340654717200165450ustar00rootroot00000000000000{ "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": { "version": "0.11.4", "hash": "4eecb4a76317039defc5c2b4bd31e4f9" }, "@_/builders": { "version": "0.11.4", "hash": "796f00a3b325334632fd8bb9d1b46b02" }, "devkit": { "version": "0.11.4", "hash": "41573426d76e924a5cdd590dd03f14db" }, "@angular/cli": { "name": "Angular CLI", "section": "Tooling", "links": [ { "label": "README", "url": "/packages/angular/cli/README.md" } ], "version": "7.1.4", "snapshotRepo": "angular/cli-builds", "hash": "697acb7a2965a0eb549d3d70d6baca6e" }, "@angular/pwa": { "name": "Angular PWA Schematics", "section": "Schematics", "version": "0.11.4", "hash": "8dfc94084f8dee26af6ef77e08c8c0f4", "snapshotRepo": "angular/angular-pwa-builds" }, "@angular-devkit/architect": { "name": "Architect", "links": [ { "label": "README", "url": "/packages/angular_devkit/architect/README.md" } ], "version": "0.11.4", "hash": "6dc4fb691ad50d08eacd64b1bc351906", "snapshotRepo": "angular/angular-devkit-architect-builds" }, "@angular-devkit/architect-cli": { "name": "Architect CLI", "version": "0.11.4", "hash": "8d55b5e2a4ac068114a747c1cadb1d8b", "snapshotRepo": "angular/angular-devkit-architect-cli-builds" }, "@angular-devkit/benchmark": { "name": "Benchmark", "section": "Tooling", "version": "1.0.4", "hash": "e36f143d472675a24d29601ed1b8c671" }, "@angular-devkit/build-optimizer": { "name": "Build Optimizer", "links": [ { "label": "README", "url": "/packages/angular_devkit/build_optimizer/README.md" } ], "version": "0.11.4", "hash": "be4ff02b13c8e11fa3207b4f4e9475f0", "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" } ], "version": "0.11.4", "hash": "24db32df6d20d10864597c2ff7dc0900", "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" } ], "version": "0.11.4", "hash": "7115bf67108f2136ea41e679138ce2d5", "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" } ], "version": "0.11.4", "snapshotRepo": "angular/angular-devkit-build-webpack-builds", "hash": "c17684526c4f579fc4e7ac62d0d357ff" }, "@angular-devkit/core": { "name": "Core", "links": [ { "label": "README", "url": "/packages/angular_devkit/core/README.md" } ], "version": "7.1.4", "hash": "256f92dd1f0b49db48fd8c1ece0faa2c", "snapshotRepo": "angular/angular-devkit-core-builds" }, "@angular-devkit/schematics": { "name": "Schematics", "links": [ { "label": "README", "url": "/packages/angular_devkit/schematics/README.md" } ], "version": "7.1.4", "hash": "fd7bc740825e731312bc5efa6e692513", "snapshotRepo": "angular/angular-devkit-schematics-builds" }, "@angular-devkit/schematics-cli": { "name": "Schematics CLI", "section": "Tooling", "version": "0.11.4", "hash": "7b1cf02e5a8f1c8d4a0eedd5c0e2f5a3", "snapshotRepo": "angular/angular-devkit-schematics-cli-builds" }, "@ngtools/webpack": { "name": "Webpack Angular Plugin", "version": "7.1.4", "section": "Misc", "hash": "54d9426dec50871c68626a5de6d40f21", "snapshotRepo": "angular/ngtools-webpack-builds" }, "@schematics/angular": { "name": "Angular Schematics", "section": "Schematics", "version": "7.1.4", "hash": "d399791bc6e93978812103444ebeec16", "snapshotRepo": "angular/schematics-angular-builds" }, "@schematics/schematics": { "name": "Schematics Schematics", "version": "0.11.4", "section": "Schematics", "hash": "85c452bd52304c6f6702495e91b87c2b", "snapshotRepo": "angular/schematics-schematics-builds" }, "@schematics/update": { "name": "Package Update Schematics", "version": "0.11.4", "section": "Schematics", "hash": "d8a5f02a59a78af20237823f13e22c12", "snapshotRepo": "angular/schematics-update-builds" } } } angular-cli-7.1.4/.nvmrc000066400000000000000000000000031340654717200150510ustar00rootroot0000000000000010 angular-cli-7.1.4/BUILD000066400000000000000000000006371340654717200145220ustar00rootroot00000000000000# 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"]) # MIT License exports_files([ "LICENSE", "tsconfig.json", # @external "tsconfig-test.json", # @external "tslint.base.json", # @external ]) angular-cli-7.1.4/CONTRIBUTING.md000066400000000000000000000270031340654717200161650ustar00rootroot00000000000000# 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) ## 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 filling out our [new issue form](https://github.com/angular/angular-cli/issues/new). ### 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 `devkit: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**: ``` ():