| 1 | The command can be used to build a project of type "application" or "library".
|
| 2 | When used to build a library, a different builder is invoked, and only the `ts-config`, `configuration`, and `watch` options are applied.
|
| 3 | All other options apply only to building applications.
|
| 4 |
|
| 5 | The application builder uses the [webpack](https://webpack.js.org/) build tool, with default configuration options specified in the workspace configuration file (`angular.json`) or with a named alternative configuration.
|
| 6 | A "production" configuration is created by default when you use the CLI to create the project, and you can use that configuration by specifying the `--configuration="production"` or the `--prod="true"` option.
|
| 7 |
|
| 8 | The configuration options generally correspond to the command options.
|
| 9 | You can override individual configuration defaults by specifying the corresponding options on the command line.
|
| 10 | The command can accept option names given in either dash-case or camelCase.
|
| 11 | Note that in the configuration file, you must specify names in camelCase.
|
| 12 |
|
| 13 | Some additional options can only be set through the configuration file,
|
| 14 | either by direct editing or with the `ng config` command.
|
| 15 | These include `assets`, `styles`, and `scripts` objects that provide runtime-global resources to include in the project.
|
| 16 | Resources in CSS, such as images and fonts, are automatically written and fingerprinted at the root of the output folder.
|
| 17 |
|
| 18 | For further details, see [Workspace Configuration](guide/workspace-config).
|