chore(deps): update dependency @angular-devkit/build-angular to v17 #833
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:
^16.0.0
->^17.0.0
Release Notes
angular/angular-cli (@angular-devkit/build-angular)
v17.0.0
Compare Source
Breaking Changes
@schematics/angular
ng generate application
andng new
. The--no-routing
command line option can be used to disable this behaviour.ng g interceptor
now generate a functional interceptor by default. or guard by default. To generate a class-based interceptor the--no-functional
command flag should be used.rootModuleClassName
,rootModuleFileName
andmain
options have been removed from the publicpwa
andapp-shell
schematics.appId
option has been removed.This change fixes a regression where using these tokens in your browser app would increase the bundle size by about ~600kb.
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.
@nguniversal/aspnetcore-engine
,@nguniversal/hapi-engine
and@nguniversal/socket-engine
has been removed in favor of@nguniversal/common
.@angular-devkit/build-angular
Node.js v16 support has been removed
Node.js v16 is planned to be End-of-Life on 2023-09-11. Angular will stop supporting Node.js v16 in Angular v17.
For Node.js release schedule details, please see: https://github.com/nodejs/release#release-schedule
@angular-devkit/schematics
runExternalSchematicAsync
andrunSchematicAsync
methods have been removed in favor ofrunExternalSchematic
andrunSchematic
.@nguniversal/common
Angular universal no longer supports Node.js versions
14.[15-19].x
and16.[10-12].x
. Current supported versions of Node.js are14.20.x
,16.13.x
and18.10.x
.Inlining of critical CSS is no longer enable by default. Users already on Angular version 12 and have not opted-out from using this feature are encouraged to opt-in using the
inlineCriticalCss
option.The motivation behind this change is that the package used to parse the CSS has a number of defects which can lead to unactionable error messages when updating to Angular 13 from versions priors to 12. Such errors can be seen in the following issue https://github.com/angular/angular-cli/issues/20760.
Support for Node.js v12 has been removed as it will become EOL on 2022-04-30. Please use Node.js v14.15 or later.
Node.js v14 support has been removed
Node.js v14 is planned to be End-of-Life on 2023-04-30. Angular will stop supporting Node.js v14 in Angular v16. Angular v16 will continue to officially support Node.js versions v16 and v18.
@nguniversal/express-engine
appDir
option was removed from the express-engine ng add schematic. This option was previously unused.express-engine
mainFactory
hapi
ngHapiEngine
is no longer supported for Hapi v16. TheRESPONSE
token provided under@nguniversal/hapi-engine/tokens
now uses the newResponseToolkit
, which is unavailable in Hapi v16. Updated instructions are available in the package's READMEuniversal
Deprecations
StateTransferInitializerModule
,TransferHttpCacheInterceptor
anddomContentLoadedFactory
have been deprecated in favor ofprovideClientHydration
. See: https://angular.io/api/platform-browser/provideClientHydration@angular-devkit/build-angular
browserTarget
in the dev-server and extract-i18n builders have been deprecated in favor ofbuildTarget
.@angular/cli
@angular/ssr
as part of the ng updatepackageGroup
@schematics/angular
ng new --ssr
@nguniversal
to@angular/ssr
@nguniversal/builders
ng new
generated applicationng new
to use the esbuild application builder based builderREQUEST
andRESPONSE
tokens@angular/ssr
during migrationesModuleInterop
by default for ESM compliancessr
option to application schematicsbaseUrl
fromtsconfig.json
@types/hapi__hapi
as they are incompatible with@hapi/inert
@angular-devkit/build-angular
buildTarget
option to dev-server andextract-i18n
buildersvite
browser-esbuild
builderbaseUrl
URL is not set to root@angular/common/locales/global
Angular is running in development mode.
in the server console when running prerender in dev modeAngular is running in development mode.
in the server console when running prerender in dev modessr
option definitionfetch
to load assets from memory@angular-devkit/schematics
runExternalSchematicAsync
andrunSchematicAsync
@angular/pwa
@angular/ssr
CommonEngine
prerender
andssr
for all build configuration@ngtools/webpack
@nguniversal/aspnetcore-engine
@nguniversal/builders
--verbose
option to SSR Dev Serverng-server-context
for SSG pageszone.js
in worker during prerendering@nguniversal/common
ng-server-context
for SSR pagesblob
andarraybuffer
in TransferHttpCacheModuleConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 Mend Renovate. View repository job log here.