Skip to content
CLI tool for Angular
TypeScript JavaScript Python HTML Shell CSS
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci ci: use windows-server-2019-vs2019:stable Dec 10, 2019
.github docs: remove backticks from bug report in command section Nov 11, 2019
.idea refactor(@angular/cli): update Intellij/Webstorm settings Nov 19, 2019
benchmark/aio build: workaround yarn tgz bug Sep 10, 2018
bin build: terminate process with non zero error code when build fails Jan 11, 2019
docs docs: fix typos in the ngConfig design document Nov 26, 2019
etc fix(@angular-devkit/schematics): hide install output by default Oct 29, 2019
lib build: set minimum Node.js version to 10.13 (#15756) Oct 10, 2019
packages build: update rollup to version 1.27.9 Dec 10, 2019
scripts build: only run ngcc hook for large tests Dec 3, 2019
tests build: update @angular/animations to version Dec 10, 2019
third_party refactor: use vendored supports-color Feb 19, 2019
tools build: should use data for fine grained npm dependencies in nodejs_bi… Oct 24, 2019
.bazelignore build: update bazel dependencies and configuration (#15291) Aug 12, 2019
.bazelrc build: remove `build:remote --spawn_strategy=remote` from .bazelrc Oct 24, 2019
.editorconfig style: update editorconfig website url (#12923) Nov 14, 2018
.gitattributes style: add .gitattributes file (#13086) Nov 30, 2018
.gitignore refactor(@angular/cli): update Intellij/Webstorm settings Nov 19, 2019
.mailmap build: add Alan to the mailmap file Jan 18, 2019
.monorepo.json docs: add Architect CLI to the "Tooling" section Jun 6, 2019
.nvmrc build: update nvmrc to use node 10 Sep 19, 2018
.prettierignore build: add golden API to prettierignore Mar 5, 2019
.prettierrc build: integrate prettier code formatting Jun 20, 2019
BUILD build: g3 sync for angular_devkit Oct 1, 2019 docs: update to reflect default PR branch (#15331) Aug 15, 2019
Dockerfile ci: use puppeteer Jan 14, 2019
LICENSE build: move devkit repo back to angular-cli Jun 6, 2018 docs(@angular/cli): Adds developer documentation. Nov 14, 2019
WORKSPACE build: update @bazel/jasmine to version 0.42.2 Dec 6, 2019
package.json build: update pacote to version 10.2.1 Dec 6, 2019
renovate.json ci: enable renovate lockFileMaintenance (#15593) Sep 18, 2019
tsconfig-test.json build: remove generation of inline sourcemaps Mar 25, 2019
tsconfig.json build: minor development tsconfig cleanup Mar 25, 2019
tslint.json style: add `no-invalid-await` and `prefer-promise-shorthand` lint rul… Aug 27, 2019
yarn.lock build: update rollup to version 1.27.9 Dec 10, 2019

Angular CLI

Development tools and libraries specialized for Angular

This is the home of the DevKit and the Angular CLI code. You can find the Angular CLI specific README here.

CircleCI branch Dependency Status devDependency Status


GitHub forks GitHub stars

Quick Links

Gitter Contributing Angular CLI

The Goal of Angular CLI

The Angular CLI creates, manages, builds and test your Angular projects. It's built on top of the Angular DevKit.

The Goal of DevKit

DevKit's goal is to provide a large set of libraries that can be used to manage, develop, deploy and analyze your code.

Getting Started - Local Development


To get started locally, follow these instructions:

  1. If you haven't done it already, make a fork of this repo.
  2. Clone to your local computer using git.
  3. Make sure that you have Node 10.13 or later installed. See instructions here.
  4. Make sure that you have yarn installed; see instructions here.
  5. Run yarn (no arguments) from the root of your clone of this project to install dependencies.

Building and Installing the CLI

To make a local build:

yarn build --local

This generates a number of tarballs in the dist/ directory. To actually use the locally built tools, switch to another repository reproducing the specific issue you want to fix (or just generate a local repo with ng new). Then install the locally built packages:

npm install -D ${CLI_REPO}/dist/*.tgz

Builds of this example project will use tooling created from the previous local build and include any local changes. When using the CLI, it will automatically check for a local install and use that if present. This means you can just run:

npm install -g @angular/cli

to get a global install of the latest CLI release. Then running any ng command in the example project will automatically find and use the local build of the CLI.

Note: If you are testing ng update, be aware that installing all the tarballs will also update the framework (@angular/core) to the latest version. In this case, simply install the CLI alone with npm install -D ${CLI_REPO}/dist/_angular_cli.tgz, that way the rest of the project remains to be upgraded with ng update.


To debug an invocation of the CLI, build and install the CLI for an example project, then run the desired ng command as:

node --inspect-brk node_modules/.bin/ng ...

This will trigger a breakpoint as the CLI starts up. You can connect to this using the supported mechanisms for your IDE, but the simplest option is to open Chrome to chrome://inspect and then click on the inspect link for the node_modules/.bin/ng Node target.

Unfortunately, the CLI dynamically require()'s other files mid-execution, so the debugger is not aware of all the source code files before hand. As a result, it is tough to put breakpoints on files before the CLI loads them. The easiest workaround is to use the debugger; statement to stop execution in the file you are interested in, and then you should be able to step around and set breakpoints as expected.


There are three different test suites which can be run locally:

  • Unit tests
    • Run: yarn test --full
    • Debug: yarn debug:test --full
  • Large tests
    • Run: yarn test-large --full
    • Debug: yarn debug:test-large --full
  • End to end tests
    • Run: node tests/legacy-cli/run_e2e.js
    • Run subset of tests: node tests/legacy-cli/run_e2e.js tests/legacy-cli/e2e/tests/i18n/ivy-localize-*

When running the debug commands, Node will stop and wait for a debugger to attach. You can attach your IDE to the debugger to stop on breakpoints and step through the code. Also see IDE Specific Usage for a simpler debug story.

When debugging a specific test, change describe() or it() to fdescribe() and fit() to focus execution to just that one test. This will keep the output clean and speed up execution by not running irrelevant tests.

IDE Specific Usage

Some additional tips for developing in specific IDEs.

Intellij IDEA / WebStorm

To load the project in Intellij products, simply Open the repository folder. Do not Import Project, because that will overwrite the existing configuration.

Once opened, the editor should automatically detect run configurations in the workspace. Use the drop down to choose which one to run and then click the Run button to start it. When executing a debug target, make sure to click the Debug icon to automatically attach the debugger (if you click Run, Node will wait forever for a debugger to attach).

Intellij IDEA run configurations

Creating New Packages

Adding a package to this repository means running two separate commands:

  1. schematics devkit:package PACKAGE_NAME. This will update the .monorepo file, and create the base files for the new package (package.json, src/index, etc).
  2. devkit-admin templates. This will update the README and all other template files that might have changed when adding a new package.

For private packages, you will need to add a "private": true key to your package.json manually. This will require re-running the template admin script.


This is a monorepo which contains many tools and packages:


Project Package Version Links
Angular CLI @angular/cli latest README snapshot
Architect CLI @angular-devkit/architect-cli latest snapshot
Schematics CLI @angular-devkit/schematics-cli latest snapshot


Project Package Version Links
Architect @angular-devkit/architect latest README snapshot
Build Angular @angular-devkit/build-angular latest README snapshot
Build NgPackagr @angular-devkit/build-ng-packagr latest README snapshot
Build Optimizer @angular-devkit/build-optimizer latest README snapshot
Build Webpack @angular-devkit/build-webpack latest README snapshot
Core @angular-devkit/core latest README snapshot
Schematics @angular-devkit/schematics latest README snapshot


Project Package Version Links
Angular PWA Schematics @angular/pwa latest snapshot
Angular Schematics @schematics/angular latest snapshot
Schematics Schematics @schematics/schematics latest snapshot
Package Update Schematics @schematics/update latest snapshot


Project Package Version Links
Webpack Angular Plugin @ngtools/webpack latest snapshot
You can’t perform that action at this time.