mirror of
https://github.com/angular/angular-cli.git
synced 2025-05-19 04:26:01 +08:00
03ce964858
The path comparisons for the TypeScript emit file lookups now use the native path normalization functions. This removes the special handling previously used and better ensures that cache checks are valid. The separate babel cache Map has also been combined with the already present memory load cache within the Angular plugin. This removes the need for extra handling of another Map and allows it to use the common logic of the load cache. To support this usage, the load cache will also now automatically include the request path in the file dependencies if the request is from the `file` namespace. This removes the need to manually specify the request path file for each load result return value.
@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.