Workspace and project configuration
A single workspace configuration file, angular.json, is created at the top level of the workspace. This 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. Note that option names in the configuration file must use camelCase, while option names supplied to commands can use either camelCase or dash-case.
CLI command-language syntax
Command syntax is shown as follows:
ng commandNameOrAlias requiredArg [optionalArg] [options]
i) Most commands, and some options, have aliases. Aliases are shown in the syntax statement for each command.
ii) Option names are prefixed with a double dash (--). Option aliases are prefixed with a single dash (-). Arguments are not prefixed. For example:
ng build my-app -c production
iii) Typically, the name of a generated artifact can be given as an argument to the command or specified with the --name option.
iv) Argument and option names can be given in either camelCase or dash-case. --myOptionName is equivalent to --my-option-name.