chore(deps): update dependency @angular-devkit/build-angular to v12 #560
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![qlty-cloud-legacy[bot]](https://avatars.githubusercontent.com/in/9403?s=60&v=4){kind=small}
satanTime
approved these changes
May 13, 2021
Member
|
v12.0.0 has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.1200.0-next.8->12.0.0Release Notes
angular/angular-cli
v12.0.0Commits
@angular-devkit/architect (0.1200.0)
@angular-devkit/build-angular (12.0.0)
@angular-devkit/build-optimizer (0.1200.0)
@angular-devkit/build-webpack (0.1200.0)
@angular-devkit/core (12.0.0)
@angular/cli (12.0.0)
@ngtools/webpack (12.0.0)
@schematics/angular (12.0.0)
[Closes #18465]
Breaking Changes
@schematics/angular: remove `stylus` from `style` options (fd729ac)
`styl` (Stylus) is no longer a supported value as `style` in `application`, `component`, `ng-new` schematics. Stylus is not actively maintained and only 0.3% of the Angular CLI users use it.(cherry picked from commit
0272fc5)@angular-devkit/build-angular: change several builder options defaults (656f8d7)
A number of browser and server builder options have had their default values changed. The aim of these changes is to reduce the configuration complexity and support the new "production builds by default" initiative.Browser builder
| Option | Previous default value | New default value |
|----------------------------------------|---------------------------|-------------------|
| optimization | false | true |
| aot | false | true |
| buildOptimizer | false | true |
| sourceMap | true | false |
| extractLicenses | false | true |
| namedChunks | true | false |
| vendorChunk | true | false |
Server builder
| Option | Previous default value | New default value |
|---------------|------------------------|-------------------|
| optimization | false | true |
| sourceMap | true | false |
(cherry picked from commit
0a74d0d)@angular-devkit/core: update schema validator (0875313)
support for JSON Schema draft-04 and draft-06 is removed. If you have schemas using the `id` keyword replace them with `$id`. For an interim period we will auto rename any top level `id` keyword to `$id`.NB: This change only effects schematics and builders authors.
@angular-devkit/build-angular: upgrade to Webpack 5 throughout the build system (d883ce5)
Webpack 5 lazy loaded file name changes Webpack 5 generates similar but differently named files for lazy loaded JavaScript files in development configurations (when the `namedChunks` option is enabled). For the majority of users this change should have no effect on the application and/or build process. Production builds should also not be affected as the `namedChunks` option is disabled by default in production configurations. However, if a project's post-build process makes assumptions as to the file names then adjustments may need to be made to account for the new naming paradigm. Such post-build processes could include custom file transformations after the build, integration into service-side frameworks, or deployment procedures. Example development file name change: `lazy-lazy-module.js` --> `src_app_lazy_lazy_module_ts.js`@ngtools/webpack: remove Webpack plugin for deprecated ViewEngine compiler (160102a)
Removal of View Engine support from application builds With the removal of the deprecated View Engine compiler in Angular version 12 for applications, the View Engine Webpack plugin has been removed. The Ivy-based Webpack plugin is the default used within the Angular CLI. If using a custom standalone Webpack configuration, the removed `AngularCompilerPlugin` should be replaced with the Ivy-based `AngularWebpackPlugin`.@angular-devkit/build-angular: remove deprecated i18n options from server and browser builder (5cf9a08)
Removal of deprecated browser and server command options. - `i18nFile`, use `locales` object in the project metadata instead. - `i18nFormat`, No longer needed as the format will be determined automatically. - `i18nLocale`, use `localize` option instead.@angular-devkit/build-angular: remove deprecated i18nLocale and i18nFormat options from i18n-extract (eca5a01)
Removal of deprecated `extract-i18n` command options The deprecated `i18nLocale` option has been removed and the `i18n.sourceLocale` within a project's configuration should be used instead. The deprecated `i18nFormat` option has been removed and the `format` option should be used instead.@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.@angular/cli: confirm ng add action before installation (985dc1a)
The `ng add` command will now ask the user to confirm the package and version prior to installing and executing an uninstalled package. This new behavior allows a user to abort the action if the version selected is not appropriate or if a typo occurred on the command line and an incorrect package would be installed. A `--skip-confirmation` option has been added to skip the prompt and directly install and execute the package. This option is useful in CI and non-TTY scenarios such as automated scripts.@angular-devkit/build-angular: remove deprecated `lazyModules` option (8d66912)
Server and Browser builder `lazyModules` option has been removed without replacement.@ngtools/webpack: drop support for string based lazy loading (0dc7327)
With this change we drop support for string based lazy loading `./lazy.module#LazyModule` use dynamic imports instead.The following options which were used to support the above syntax were removed without replacement.
@angular-devkit/build-angular: enable inlineCritical by default (aa3ea88)
Critical CSS inlining is now enabled by default. If you wish to turn this off set `inlineCritical` to `false`.See: https://angular.io/guide/workspace-config#optimization-configuration
@angular-devkit/build-angular: drop support for zone.js 0.10 (f309516)
Minimum supported `zone.js` version is `0.11.4`@angular-devkit/build-angular: drop support for ng-packagr version 11 (44e75be)
Minimum supported `ng-packagr` version is `12.0.0-next`@angular-devkit/build-angular: drop support for karma version 5.2 (fa5cf53)
Minimum supported `karma` version is `6.0.0`set minimum Node.js version to 12.13 (d1f6169)
Node.js version 10 will become EOL on 2021-04-30. Angular CLI 12 will require Node.js 12.13+ or 14.15+. Node.js 12.13 and 14.15 are the first LTS releases for their respective majors.@angular-devkit/build-angular: remove file-loader dependency (6732294)
The unsupported/undocumented, Webpack specific functionality to `import`/`require()` a non-module file has been removed.Before
After
Special Thanks
Alan Agius, Charles Lyding, Keen Yee Liau, Joey Perrott, Doug Parker, Cédric Exbrayat, Douglas Parker, George Kalpakas, Sam Bulatov, Joshua Chapman, Santosh Yadav, David Shevitz, Kristiyan Kostadinov
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.