Delegates the build to a different target while supporting incremental builds.
Here is a list of all executor available for this package.
Builds a library with support for incremental builds. This executor is meant to be used with buildable libraries in an incremental build scenario. It is similar to the
@nrwl/angular:packageexecutor but with some key differences:
- It doesn't run
ngccneeds to be run separately beforehand if needed, this can be done in a
- It only produces ESM2020 bundles.
- It doesn't generate package exports in the
- It doesn't run
Builds and packages an Angular library producing an output following the Angular Package Format (APF) to be distributed as an NPM package. This executor is similar to the
@angular-devkit/build-angular:ng-packagrwith additional support for incremental builds.
Builds your application with esbuild and adds support for incremental builds.
The module-federation-dev-server executor is reserved exclusively for use with host Module Federation applications. It allows the user to specify which remote applications should be served with the host.
Builds an application with esbuild with support for incremental builds. Note: this is only supported in Angular versions >= 17.0.0.
Extracts i18n messages from source code.
webpack-browserexecutor is very similar to the standard
browserbuilder 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
webpack-serverexecutor is very similar to the standard
serverbuilder provided by the Angular Devkit. It is usually used in tandem with
@nrwl/angular:webpack-browserwhen your Angular application uses a custom webpack configuration and NgUniversal for SSR.
The module-federation-dev-ssr executor is reserved exclusively for use with host Module Federation applications that use SSR. It allows the user to specify which remote applications should be served with the host.