Update Angular to v18 (major) #231
Open
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
renovate
bot
force-pushed
the
renovate/major-angular
branch
from
f7e6a50
to
1dadc36
Compare
renovate
bot
force-pushed
the
renovate/major-angular
branch
from
1dadc36
to
3673273
Compare
renovate
bot
force-pushed
the
renovate/major-angular
branch
from
3673273
to
d4740e1
Compare
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:
^17.3.6->^18.0.0^17.3.0->^18.0.0^17.3.6->^18.0.0^17.3.6->^18.0.0^17.3.6->^18.0.0^17.3.6->^18.0.0^17.3.6->^18.0.0^17.3.6->^18.0.0^17.3.6->^18.0.0^17.0.1->^18.0.0^17.3.6->^18.0.0^17.3.6->^18.0.0^17.3.6->^18.0.0^17.3.6->^18.0.0^17.3.6->^18.0.0^17.3.6->^18.0.0^17.0.0->^18.0.0^17.0.0->^18.0.0Release Notes
angular/angular-cli (@angular-devkit/build-angular)
v18.0.4Compare Source
@angular/build
@angular/localize/initv18.0.3Compare Source
@angular/cli
schema.jsonoptions to parsed command, also when a version is passed tong add <package>@​<version>@angular/build
v18.0.2Compare Source
@schematics/angular
assetsoption correctly for new applications@angular/build
@warnlocation@angular/pwa
iconslocation to matchassetsbuilder optionv18.0.1Compare Source
@schematics/angular
@angular/build
polyfillsoption asstringduringng servev18.0.0Compare Source
Breaking Changes
@angular/cli
ng doccommand has been removed without a replacement. To perform searches, please visit www.angular.dev@angular-devkit/build-angular
By default, the index.html file is no longer emitted in the browser directory when using the application builder with SSR. Instead, an index.csr.html file is emitted. This change is implemented because in many cases server and cloud providers incorrectly treat the index.html file as a statically generated page. If you still require the old behavior, you can use the
indexoption to specify theoutputfile name.The support for the legacy Sass build pipeline, previously accessible via
NG_BUILD_LEGACY_SASSwhen utilizing webpack-based builders, has been removed.Deprecations
@angular-devkit/schematics
NodePackageLinkTaskin@angular-devkit/schematics. A custom task should be created instead.@angular/cli
ng devalias tong serve--versionoption@angular/buildpackage to update group listng versioncommandng doccommand@schematics/angular
assetswithpublicdirectory@angular-devkit/architect
@angular-devkit/build-angular
polloption in the library builderindex.htmlfile in the browser directory when using SSR.@angular-devkit/schematics
NodePackageLinkTask@angular/build
ansi-colorsandpicomatchdependenciesv17.3.8Compare Source
@angular/cli
@angular-devkit/schematics
SchematicTestRunner.runExternalSchematicfails with "The encoded data was not valid for encoding utf-8"v17.3.7Compare Source
angular-eslint/angular-eslint (@angular-eslint/eslint-plugin)
v18.0.1Compare Source
🩹 Fixes
❤️ Thank You
v18.0.0Compare Source
🚀 Features
❤️ Thank You
17.5.2 (2024-05-28)
🩹 Fixes
17.5.1 (2024-05-23)
🩹 Fixes
17.5.0 (2024-05-22)
🚀 Features
🩹 Fixes
update dependency @angular/compiler to v17.3.9
update typescript-eslint packages to v7.10.0
eslint-plugin: [no-input-rename] incorrectly triggers on input transforms
❤️ Thank You
17.4.1 (2024-05-15)
🩹 Fixes
❤️ Thank You
17.4.0 (2024-05-07)
🚀 Features
🩹 Fixes
update dependency @angular/compiler to v17.3.4
update dependency eslint-scope to v8.0.1
update typescript-eslint packages to v7.6.0
update typescript-eslint packages to v7.7.0
update dependency @angular/compiler to v17.3.6
update typescript-eslint packages to v7.8.0
eslint-plugin: [sort-ngmodule-metadata-arrays] deprecate rule
❤️ Thank You
17.3.0 (2024-03-15)
🚀 Features
eslint-plugin: consistent-component-styles
eslint-plugin: add prefer-standalone rule for checking all directives
🩹 Fixes
update dependency tmp to v0.2.3
migrate to nx 18
update dependency ignore to v5.3.1
update dependency eslint to v8.57.0
update typescript-eslint packages to v7 (major)
update dependency @angular/compiler to v17.3.0
output declaration files in all packages
❤️ Thank You
17.2.1 (2024-01-20)
🩹 Fixes
update typescript-eslint packages to v6.18.1
update typescript-eslint packages to v6.19.0
update dependency @angular/compiler to v17.1.0
❤️ Thank You
17.2.0 (2024-01-06)
🚀 Features
🩹 Fixes
update dependency eslint to v8.56.0
update typescript-eslint packages to v6.18.0
update dependency @angular/compiler to v17.0.8
update dependency eslint-scope to v8
❤️ Thank You
17.1.1
🩹 Fixes
update nrwl monorepo to v17.1.3
update typescript-eslint packages to v6.12.0
update dependency ignore to v5.3.0
update dependency eslint to v8.54.0
update typescript-eslint packages to v6.13.0
update typescript-eslint packages to v6.13.1
eslint-plugin: fix max inline declarations rule for styles string
❤️ Thank You
17.1.0
This was a version bump only for eslint-plugin to align it with other projects, there were no code changes.
v17.5.2Compare Source
🩹 Fixes
v17.5.1Compare Source
🩹 Fixes
v17.5.0Compare Source
🚀 Features
🩹 Fixes
update dependency @angular/compiler to v17.3.9
update typescript-eslint packages to v7.10.0
eslint-plugin: [no-input-rename] incorrectly triggers on input transforms
❤️ Thank You
v17.4.1Compare Source
🩹 Fixes
❤️ Thank You
v17.4.0Compare Source
🚀 Features
🩹 Fixes
update dependency @angular/compiler to v17.3.4
update dependency eslint-scope to v8.0.1
update typescript-eslint packages to v7.6.0
update typescript-eslint packages to v7.7.0
update dependency @angular/compiler to v17.3.6
update typescript-eslint packages to v7.8.0
eslint-plugin: [sort-ngmodule-metadata-arrays] deprecate rule
❤️ Thank You
angular/angular (@angular/animations)
v18.0.3Compare Source
benchpress
core
localize
@angular/localize/initas polyfill inangular.json(#56300)migrations
v18.0.2Compare Source
core
HttpClientModuleimports on components. (#56067)withI18nSupport()call for components that use i18n blocks (#56175)migrations
v18.0.1Compare Source
compiler
compiler-cli
core
migrations
v18.0.0Compare Source
Blog post "Angular v18 is now available".
Breaking Changes
animations
matchesElementmethod has been removed fromAnimationDriveras it is unused.common
isPlatformWorkerUiandisPlatformWorkerApphave been removed without replacement, as they serve no purpose since the removal of the WebWorker platform.compiler
compiler-cli
core
OnPushviews at the root of the application need tobe marked dirty for their host bindings to refresh. Previously, the host
bindings were refreshed for all root views without respecting the
OnPushchange detection strategy.OnPushviews at the root of the application need tobe marked dirty for their host bindings to refresh. Previously, the host
bindings were refreshed for all root views without respecting the
OnPushchange detection strategy.The
ComponentFixtureautoDetectfeature will nolonger refresh the component's host view when the component is
OnPushand not marked dirty. This exposes existing issues in components which
claim to be
OnPushbut do not correctly callmarkForCheckwhen theyneed to be refreshed. If this change causes test failures, the easiest
fix is to change the component to
ChangeDetectionStrategy.Default.ComponentFixture.whenStablenow matches theApplicationRef.isStableobservable. Prior to this change, stabilityof the fixture did not include everything that was considered in
ApplicationRef.whenStableof the fixture will now include unfinishedrouter navigations and unfinished
HttpClientrequests. This will causetests that
awaitthewhenStablepromise to time out when there areincomplete requests. To fix this, remove the
whenStable,instead wait for another condition, or ensure
HttpTestingControllermocks responses for all requests. Try adding
HttpTestingController.verify()before your
await fixture.whenStableto identify the open requests.Also, make sure your tests wait for the stability promise. We found many
examples of tests that did not, meaning the expectations did not execute
within the test body.
In addition,
ComponentFixture.isStablewould synchronously switch totrue in some scenarios but will now always be asynchronous.
Angular will ensure change detection runs, even when the state update originates from
outside the zone, tests may observe additional rounds of change
detection compared to the previous behavior.
This change will be more likely to impact existing unit tests.
This should usually be seen as more correct and the test should be updated,
but in cases where it is too much effort to debug, the test can revert to the old behavior by adding
provideZoneChangeDetection({schedulingMode: NgZoneSchedulingMode.NgZoneOnly})to the
TestBedproviders.Similarly, applications which may want to update state outside the zone
and not trigger change detection can add
provideZoneChangeDetection({schedulingMode: NgZoneSchedulingMode.NgZoneOnly})to the providers in
bootstrapApplicationor addschedulingMode: NgZoneSchedulingMode.NgZoneOnlyto theBootstrapOptionsofbootstrapModule.When Angular runs change detection, it will continue to
refresh any views attached to
ApplicationRefthat are still marked forcheck after one round completes. In rare cases, this can result in infinite
loops when certain patterns continue to mark views for check using
ChangeDetectorRef.detectChanges. This will be surfaced as a runtimeerror with the
NG0103code.asynchas been removed, usewaitForAsyncinstead.The
ComponentFixture.autoDetectfeature now executeschange detection for the fixture within
ApplicationRef.tick. This moreclosely matches the behavior of how a component would refresh in
production. The order of component refresh in tests may be slightly
affected as a result, especially when dealing with additional components
attached to the application, such as dialogs. Tests sensitive to this
type of change (such as screenshot tests) may need to be updated.
Concretely, this change means that the component will refresh before
additional views attached to
ApplicationRef(i.e. dialog components).Prior to this change, the fixture component would refresh after other
views attached to the application.
The exact timing of change detection execution when
using event or run coalescing with
NgZoneis now the first of eithersetTimeoutorrequestAnimationFrame. Code which relies on thistiming (usually by accident) will need to be adjusted. If a callback
needs to execute after change detection, we recommend
afterNextRenderinstead of something like
setTimeout.Newly created and views marked for check and reattached
during change detection are now guaranteed to be refreshed in that same
change detection cycle. Previously, if they were attached at a location
in the view tree that was already checked, they would either throw
ExpressionChangedAfterItHasBeenCheckedErroror not be refreshed untilsome future round of change detection. In rare circumstances, this
correction can cause issues. We identified one instance that relied on
the previous behavior by reading a value on initialization which was
queued to be updated in a microtask instead of being available in the
current change detection round. The component only read this value during
initialization and did not read it again after the microtask updated it.
Testability methods
increasePendingRequestCount,decreasePendingRequestCountandgetPendingRequestCounthave beenremoved. This information is tracked with zones.
http
By default we now prevent caching of HTTP requests that require authorization . To opt-out from this behaviour use the
includeRequestsWithAuthHeadersoption inwithHttpTransferCache.Example:
platform-browser
StateKey,TransferStateandmakeStateKeyhave been removed from@angular/platform-browser, use the same APIs from@angular/core.platform-browser-dynamic
RESOURCE_CACHE_PROVIDERAPIs have been removed.platform-server
deprecated
platformDynamicServerhas been removed. Add animport @​angular/compilerand replace the usage withplatformServerdeprecated
ServerTransferStateModulehas been removed.TransferStatecan be use without providing this module.deprecated
useAbsoluteUrlandbaseUrlbeen removed fromPlatformConfig. Provide and absoluteurlinstead.Legacy handling or Node.js URL parsing has been removed from
ServerPlatformLocation.The main differences are;
pathnameis always suffixed with a/.portis empty whenhttp:protocol and port in url is80portis empty whenhttps:protocol and port in url is443router
RedirectCommandfor redirectsin addition to
UrlTree. Code which expects only `booleanConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate. View repository job log here.