Builder oriented toward Ionic

angular-cli-builders

A set of additional builders for Angular CLI.
Allows customizing the build configuration without ejecting webpack configuration (ng eject)

Prerequisites:

• Angular CLI 6
• @angular-devkit/architect >= 0.7.0
• @angular-devkit/build-angular >= 0.7.0
• @angular-devkit/core >= 0.7.0

Usage

1. npm i -D angular-cli-builders
2. In your angular.json:

   ...
   "architect": {
          ...
          "[architect-target]": {
                    "builder": "angular-cli-builders:[name-of-builder]"
                    "options": {
                          ...
                    }

   Where:
   • [architect-target] is the name of build target you want to run (build, serve, test etc.)
   • [name-of-builder] one of the supported builders (specified below)
3. ng [architect-target]

For example

• angular.json:

  "architect": {
      ...
      "build": {
                "builder": "angular-builders:custom-webpack-browser"
                "options": {
                      ...
                }

• Run the build: ng build

Builders

• custom-webpack-browser
• custom-webpack-server
• generic-dev-server

custom-webpack-browser

Extended @angular-devkit/build-angular:browser builder that allows to specify additional webpack configuration (on top of the existing under the hood). The builder will run the same build as @angular-devkit/build-angular:browser does with extra parameters that are specified in the provided webpack configuration.

Options:

• All the @angular-devkit/build-angular:browser options
• customWebpackConfig: configuration object with the following properties:
  • path: path to the extra webpack configuration, defaults to webpack.config.js
  • mergeStrategies: webpack config merge strategies, can be append | prepend | replace per webpack config entry. Defaults to append.
    • append: appends the given entry configuration (in custom webpack config) to the existing Angular CLI webpack configuration.
    • prepend: prepends the given entry configuration (in custom webpack config) to the existing field configuration (in Angular CLI webpack config). The custom loaders config will be added to the beginning of the existing loaders array.
    • replace: replaces the given entry configuration entirely. The custom webpack config will replace the Angular CLI webpack config (for this particular entry). See webpack-merge for more info.
  • replaceDuplicatePlugins: Defaults to false. If true, the plugins in custom webpack config will replace the corresponding plugins in default Angular CLI webpack configuration.

angular.json Example:

"architect": {
    ...
    "build": {
              "builder": "angular-cli-builders:custom-webpack-browser"
              "options": {
                     "customWebpackConfig": {
                        path: "./extra-webpack.config.js",
                        mergeStrategies: { "externals": "prepend" },
                     }
                     "outputPath": "dist/my-cool-client",
                     "index": "src/index.html",
                     "main": "src/main.ts",
                     "polyfills": "src/polyfills.ts",
                     "tsConfig": "src/tsconfig.app.json"
              }

In this example externals entry from extra-webpack.config.js will be prepended to externals entry from Angular CLI underlying webpack config.

custom-webpack-server

Extended @angular-devkit/build-angular:server builder that allows to specify additional webpack configuration (on top of the existing under the hood). The builder will run the same build as @angular-devkit/build-angular:server does with extra parameters that are specified in the provided webpack configuration.

Options:

• All the @angular-devkit/build-angular:server options
• customWebpackConfig: configuration object with the following properties:
  • path: path to the extra webpack configuration, defaults to webpack.config.js
  • mergeStrategies: webpack config merge strategies, can be append | prepend | replace per webpack config entry. Defaults to append.
    • append: appends the given entry configuration (in custom webpack config) to the existing Angular CLI webpack configuration.
    • prepend: prepends the given entry configuration (in custom webpack config) to the existing field configuration (in Angular CLI webpack config). The custom loaders config will be added to the beginning of the existing loaders array.
    • replace: replaces the given entry configuration entirely. The custom webpack config will replace the Angular CLI webpack config (for this particular entry). See webpack-merge for more info.
  • replaceDuplicatePlugins: Defaults to false. If true, the plugins in custom webpack config will replace the corresponding plugins in default Angular CLI webpack configuration.

angular.json Example:

"architect": {
    ...
    "build": {
              "builder": "angular-cli-builders:custom-webpack-server"
              "options": {
                     "customWebpackConfig": {
                        path: "./extra-webpack.config.js",
                        mergeStrategies: { "loaders": "replace" },
                        replaceDuplicatePlugins: true
                     }
                    "outputPath": "dist/my-cool-server",
                    "main": "src/main.server.ts",
                    "tsConfig": "src/tsconfig.server.json"
              }

In this example loaders entry from Angular CLI webpack config will be replaced with loaders entry from extra-webpack.config.js. The plugins from extra-webpack.config.js will override the corresponding plugins from Angular CLI webpack config.

generic-dev-server

Enhanced @angular-devkit/build-angular:dev-server builder that leverages the custom webpack builder to get webpack configuration. Unlike the default @angular-devkit/build-angular:dev-server it doesn't use @angular-devkit/build-angular:browser configuration to run the dev server. Instead it uses a builder that is specified in browserTarget as long as it provides buildWebpackConfig method.
Thus, if you use generic-dev-server along with custom-webpack-browser, ng serve will run with custom configuration provided in the latter.

angular.json Example

"architect": {
    ...
    "build": {
        "builder": "angular-cli-builders:custom-webpack-browser"
        "options": {
            "webpackConfigPath": "./extra-webpack.config.js",
            "mergeStrategy": { "loaders": "replace" },
            ...
        },
    "serve": {
        "builder": "angular-cli-builders:generic-dev-server",
        "options": {
            "browserTarget": "my-project:build"
        }
    }

In this example the dev-server will use the webpack builder from the custom-webpack-browser when invoking the serve target.

Further reading

• Customizing Angular CLI 6 build  -  an alternative to ng eject