mirror of
https://github.com/angular/angular-cli.git
synced 2025-05-18 20:02:40 +08:00
When using the `application` or `browser-esbuild` builders, a parallel TS/NG compilation will be used by default via a Node.js Worker. However, when used inside a Web Container, the build will fail to initialize the compilation instance due to what appears to be a defect within Web containers involving the transfer/serialization of a MessageChannel's MessagePort objects. To avoid this problem, the parallel compilation is disabled by default when the build system detects it is being executed from within a Web Container. A parallel compilation can still be forced by using the `NG_BUILD_PARALLEL_TS=1` environment variable.
@angular-devkit/build-angular
This package contains Architect builders used to build and test Angular applications and libraries.
Builders
Name | Description |
---|---|
application | Build an Angular application targeting a browser and server environment using esbuild. |
app-shell | Build an Angular App shell. |
browser | Build an Angular application targeting a browser environment using Webpack. |
browser-esbuild | Build an Angular application targeting a browser environment using esbuild. |
dev-server | A development server that provides live reloading. |
extract-i18n | Extract i18n messages from an Angular application. |
karma | Execute unit tests using Karma test runner. |
ng-packagr | Build and package an Angular library in Angular Package Format (APF) format using ng-packagr. |
prerender | Prerender pages of your application. Prerendering is the process where a dynamic page is processed at build time generating static HTML. |
server | Build an Angular application targeting a Node.js environment. |
ssr-dev-server | A development server which offers live reload during development, but uses server-side rendering. |
protractor | Deprecated - Run end-to-end tests using Protractor framework. |
Disclaimer
While the builders when executed via the Angular CLI and their associated options are considered stable, the programmatic APIs are not considered officially supported and are not subject to the breaking change guarantees of SemVer.