Commits
@angular-devkit/build-angular (0.1200.0-next.7) | ||
| Commit | Description | Notes |
|
| validate scripts and styles bundleName |
[Closes #20360] |
|
| remove deprecated View Engine support for i18n extraction | |
|
| remove usage of deprecated View Engine compiler | |
@angular/cli (12.0.0-next.7) | ||
| Commit | Description | Notes |
|
| ensure update migrations are fully executed | |
|
| exclude deprecated packages with removal migrations from update | |
@ngtools/webpack (12.0.0-next.7) | ||
| Commit | Description | Notes |
|
| use correct Webpack asset stage in resource loader | |
|
| only check affected files for Angular semantic diagnostics | |
@schematics/angular (12.0.0-next.7) | ||
| Commit | Description | Notes |
|
| remove `entryComponent` from `component` schematic | |
|
| correctly handle adding multi-line strings to `@NgModule` metadata | |
|
| explicitly specify ServiceWorker registration strategy | |
Breaking Changes
@angular-devkit/build-angular: remove usage of deprecated View Engine compiler (677913f)
Removal of View Engine support from application builds With the removal of the deprecated View Engine compiler in Angular version 12 for applications, Ivy-based compilation will always be used when building an application. The default behavior for applications is to use the Ivy compiler when building and no changes are required for these applications. For applications that have opted-out of Ivy, a warning will be shown and an Ivy-based build will be attempted. If the build fails, the application may need to be updated to become Ivy compatible.@schematics/angular: remove `entryComponent` from `component` schematic (8582ddc)
`entryComponent` option has been removed from the `component` schematic as this was intended to be used with the the now no longer supported ViewEngine rendering engine.@angular-devkit/build-angular: remove view engine app-shell generation (1c2aeeb)
App-shell builder now only supports generation using Ivy@angular-devkit/build-angular: remove deprecated View Engine support for i18n extraction (012700a)
Removal of View Engine support from i18n extraction With the removal of the deprecated View Engine compiler in Angular version 12 for applications, the `ng extract-i18n` command will now always use the Ivy compiler. The `--ivy` option has also been removed as Ivy-based extraction is always enabled. The default behavior for applications is to use the Ivy compiler for building/extraction and no changes are required for these applications. For applications that have opted-out of Ivy, a warning will be shown and Ivy-based extraction will be attempted. If the extraction fails, the application may need to be updated to become Ivy compatible.Special Thanks
Charles Lyding, Alan Agius, Renovate Bot, George Kalpakas, Joey Perrott, Keen Yee Liau