@nrwl/angular:webpack-browser
The webpack-browser executor is very similar to the standard browser builder provided by the Angular Devkit. It allows you to build your Angular application to a build artifact that can be hosted online. There are some key differences:
- Supports Custom Webpack Configurations
- Supports Incremental Building
Options can be configured in project.json when defining the executor, or when invoking it. Read more about how to configure targets and executors here: https://nx.dev/configuration/projectjson#targets.
Using a custom webpack configuration
The executor supports providing a path to a custom webpack configuration. This allows you to customize how your Angular application is built. It currently supports the following types of webpack configurations:
objectFunctionPromise<object|Function>
The executor will merge the provided configuration with the webpack configuration that Angular Devkit uses. The merge order is:
- Angular Devkit Configuration
- Provided Configuration
To use a custom webpack configuration when building your Angular application, change the build target in your project.json to match the following:
1"build": {
2 "executor": "@nrwl/angular:webpack-browser",
3 "options": {
4 ...
5 "customWebpackConfig": {
6 "path": "apps/appName/webpack.config.js"
7 }
8 }
9}Incrementally Building your Application
The executor supports incrementally building your Angular application by building the workspace libraries it depends on (that have been marked as buildable) and then building your application using the built source of the libraries.
This can improve build time as the building of the workspace libraries can be cached, meaning they only have to be rebuilt if they have changed.
Note: There may be some additional overhead in the linking of the built libraries' sources which may reduce the overall improvement in build time. Therefore this approach only benefits large applications and would likely have a negative impact on small and medium applications.
You can read more about when to use incremental builds here.
To allow your Angular application to take advantage of incremental building, change the build target in your project.json to match the following:
1"build": {
2 "executor": "@nrwl/angular:webpack-browser",
3 "options": {
4 ...
5 "buildLibsFromSource": false
6 }
7}Options
aot
trueBuild using Ahead of Time compilation.
allowedCommonJsDependencies
[]A list of CommonJS packages that are allowed to be used without a build time warning.
baseHref
Base url for the application being built.
buildOptimizer
trueEnables '@angular-devkit/build-optimizer' optimizations when using the 'aot' option.
budgets
[]Budget thresholds to ensure parts of your application stay within boundaries which you set.
buildLibsFromSource
trueRead buildable libraries from source instead of building them separately.
commonChunk
trueGenerate a seperate bundle containing code used across multiple bundles.
crossOrigin
nonenone, anonymous, use-credentialsDefine the crossorigin attribute setting of elements that provide CORS support.
deployUrl
URL where files will be deployed.
Use baseHref option, APP_BASE_HREF DI token or a combination of both instead. For more information, see https://angular.io/guide/deployment#the-deploy-url.
deleteOutputPath
trueDelete the output path before building.
extractLicenses
trueExtract all licenses in a separate file.
fileReplacements
Replace compilation source files with other compilation source files in the build.
inlineStyleLanguage
csscss, less, sass, scssThe stylesheet language to use for the application's inline component styles.
i18nMissingTranslation
warningwarning, error, ignoreHow to handle missing translations for i18n.
i18nDuplicateTranslation
warningwarning, error, ignoreHow to handle duplicate translations for i18n.
localize
Translate the bundles in one or more locales.
main
The full path for the main entry point to the app, relative to the current workspace.
namedChunks
falseUse file name for lazy loaded chunks.
ngswConfigPath
Path to ngsw-config.json.
optimization
trueEnables optimization of the build output. Including minification of scripts and styles, tree-shaking, dead-code elimination, inlining of critical CSS and fonts inlining. For more information, see https://angular.io/guide/workspace-config#optimization-configuration.
outputPath
The full path for the new output directory, relative to the current workspace.
By default, writes output to a folder named dist/ in the current project.
outputHashing
nonenone, all, media, bundlesDefine the output filename cache-busting hashing mode.
polyfills
The full path for the polyfills file, relative to the current workspace.
progress
trueLog progress to the console while building.
poll
Enable and define the file watching poll time period in milliseconds.
preserveSymlinks
Do not use the real path when resolving modules. If unset then will default to true if NodeJS option --preserve-symlinks is set.
resourcesOutputPath
The path where style resources will be placed, relative to outputPath.
sourceMap
falseOutput source maps for scripts and styles. For more information, see https://angular.io/guide/workspace-config#source-map-configuration.
showCircularDependencies
falseShow circular dependency warnings on builds.
The recommended method to detect circular dependencies in project code is to use either a lint rule or other external tooling.
subresourceIntegrity
falseEnables the use of subresource integrity validation.
serviceWorker
falseGenerates a service worker config for production builds.
statsJson
falseGenerates a 'stats.json' file which can be analyzed using tools such as 'webpack-bundle-analyzer'.
tsConfig
The full path for the TypeScript configuration file, relative to the current workspace.
vendorChunk
falseGenerate a seperate bundle containing only vendor libraries. This option should only used for development.
verbose
falseAdds more details to output logging.
watch
falseRun build when files change.
webWorkerTsConfig
TypeScript configuration for Web Worker modules.