The Angular CLI is a command-line interface tool that you use to initialize, develop, scaffold, and maintain Angular applications directly from a command shell.
\nMajor versions of Angular CLI follow the supported major version of Angular, but minor versions can be released separately.
\nInstall the CLI using the npm package manager:\n
For details about changes between versions, and information about updating from previous releases,\nsee the Releases tab on GitHub: https://github.com/angular/angular-cli/releases
\nInvoke the tool on the command line through the ng executable.\nOnline help is available on the command line.\nEnter the following to list commands or options for a given command (such as generate) with a short description.
To create, build, and serve a new, basic Angular project on a development server, go to the parent directory of your new workspace use the following commands:
\nIn your browser, open http://localhost:4200/ to see the new app run.\nWhen you use the ng serve command to build an app and serve it locally, the server automatically rebuilds the app and reloads the page when you change any of the source files.
\n When you run ng new my-first-project a new folder, named my-first-project, will be created in the current working directory. Since you want to be able to create files inside that folder, make sure you have sufficient rights in the current working directory before running the command.
If the current working directory is not the right place for your project, you can change to a more appropriate directory by running cd <path-to-other-directory> first.
The ng new command creates an Angular workspace folder and generates a new app skeleton.\nA workspace can contain multiple apps and libraries.\nThe initial app created by the ng new command is at the top level of the workspace.\nWhen you generate an additional app or library in a workspace, it goes into a projects/ subfolder.
A newly generated app contains the source files for a root module, with a root component and template.\nEach app has a src folder that contains the logic, data, and assets.
You can edit the generated files directly, or add to and modify them using CLI commands.\nUse the ng generate command to add new files for additional components and services, and code for new pipes, directives, and so on.\nCommands such as add and generate, which create or operate on apps and libraries, must be executed from within a workspace or project folder.
\nA single workspace configuration file, angular.json, is created at the top level of the workspace.\nThis is where you can set per-project defaults for CLI command options, and specify configurations to use when the CLI builds a project for different targets.
The ng config command lets you set and retrieve configuration values from the command line, or you can edit the angular.json file directly.\nNote that option names in the configuration file must use camelCase, while option names supplied to commands can use either camelCase or dash-case.
angular.json.Command syntax is shown as follows:
\nng commandNameOrAlias requiredArg [optionalArg] [options]
Most commands, and some options, have aliases. Aliases are shown in the syntax statement for each command.
\nOption names are prefixed with a double dash (--).\nOption aliases are prefixed with a single dash (-).\nArguments are not prefixed.\nFor example:\n
Typically, the name of a generated artifact can be given as an argument to the command or specified with the --name option.
\nArgument and option names can be given in either\ncamelCase or dash-case.\n--myOptionName is equivalent to --my-option-name.
Boolean options have two forms: --this-option sets the flag to true, --no-this-option sets it to false.\nIf neither option is supplied, the flag remains in its default state, as listed in the reference documentation.
Options that specify files can be given as absolute paths, or as paths relative to the current working directory, which is generally either the workspace or project root.
\nThe ng generate and ng add commands take as an argument the artifact or library to be generated or added to the current project.\nIn addition to any general options, each artifact or library defines its own options in a schematic.\nSchematic options are supplied to the command in the same format as immediate command options.
\n\n| Command | \nAlias | \nDescription | \n
|---|---|---|
add | \n \n | Adds support for an external library to your project. \n | \n
analytics | \n \n | Configures the gathering of Angular CLI usage metrics. See https://angular.io/cli/usage-analytics-gathering. \n | \n
build | \n b | \n Compiles an Angular app into an output directory named dist/ at the given output path. Must be executed from within a workspace directory. \n | \n
config | \n \n | Retrieves or sets Angular configuration values in the angular.json file for the workspace. \n | \n
deploy | \n \n | Invokes the deploy builder for a specified project or for the default project in the workspace. \n | \n
doc | \n d | \n Opens the official Angular documentation (angular.io) in a browser, and searches for a given keyword. \n | \n
e2e | \n e | \n Builds and serves an Angular app, then runs end-to-end tests using Protractor. \n | \n
extract-i18n | \n i18n-extract xi18n | \n Extracts i18n messages from source code. \n | \n
generate | \n g | \n Generates and/or modifies files based on a schematic. \n | \n
help | \n \n | Lists available commands and their short descriptions. \n | \n
lint | \n l | \n Runs linting tools on Angular app code in a given project folder. \n | \n
new | \n n | \n Creates a new workspace and an initial Angular application. \n | \n
run | \n \n | Runs an Architect target with an optional custom builder configuration defined in your project. \n | \n
serve | \n s | \n Builds and serves your app, rebuilding on file changes. \n | \n
test | \n t | \n Runs unit tests in a project. \n | \n
update | \n \n | Updates your application and its dependencies. See https://update.angular.io/ \n | \n
version | \n v | \n Outputs Angular CLI version. \n | \n