chore(deps): update angular monorepo to v19 (major) #175
+37
−37
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}
|
![kodiakhq[bot]](https://avatars.githubusercontent.com/in/29196?s=60&v=4){kind=small}
✅ Deploy Preview for plugin-angular-universal-demo ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
github-actions
bot
added
the
type: chore
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:
^18.0.1->^19.0.0-next^18.1.0-rc->^19.0.0-next^18.1.0-rc->^19.0.0-next^18.1.0-rc->^19.0.0-next^18.1.0-rc->^19.0.0-next^18.0.1->^19.0.0-next^18.1.0-rc->^19.0.0-next^18.1.0-rc->^19.0.0-next^18.1.0-rc->^19.0.0-next^18.0.1->^19.0.0-nextRelease Notes
angular/angular (@angular/animations)
v19.0.0-next.2Compare Source
Breaking Changes
core
Render default fallback with empty
projectableNodes.When passing an empty array to
projectableNodesin thecreateComponentAPI, the default fallback content of theng-contentwill be rendered if present. To prevent rendering the default content, passdocument.createTextNode('')as aprojectableNode.For example:
The timers that are used for zone coalescing and hybrid
mode scheduling (which schedules an application state synchronization
when changes happen outside the Angular zone) will now run in the zone
above Angular rather than the root zone. This will mostly affect tests
which use
fakeAsync: these timers will now be visible tofakeAsyncand can be affected by
tickorflush.elements
hybrid scheduler, timing of change detection around custom elements has
changed subtly. These changes make elements more efficient, but can cause
tests which encoded assumptions about how or when elements would be checked
to require updating.
common
compiler-cli
core
elements
ComponentRef.setInput& remove custom scheduler (#56728)router
upgrade
v19.0.0-next.1Compare Source
Breaking Changes
core
autoDetectfeature ofComponentFixturewill nowattach the fixture to the
ApplicationRef. As a result, errors duringautomatic change detection of the fixture be reported to the
ErrorHandler.This change may cause custom error handlers to observe new failures that were previously unreported.
compiler-cli
core
fakeAsync(#56932)migrations
v19.0.0-next.0Compare Source
Breaking Changes
core
Errors that are thrown during
ApplicationRef.tickwill now be rethrown when using
TestBed. These errors should beresolved by ensuring the test environment is set up correctly to
complete change detection successfully. There are two alternatives to
catch the errors:
it synchronously and expect the error. For example, a jasmine test
could write
expect(() => TestBed.inject(ApplicationRef).tick()).toThrow()TestBedwill reject any outstandingComponentFixture.whenStablepromises. A jasmine test,for example, could write
expectAsync(fixture.whenStable()).toBeRejected().As a last resort, you can configure errors to not be rethrown by
setting
rethrowApplicationErrorstofalseinTestBed.configureTestingModule.router
Router.errorHandlerproperty has been removed.Adding an error handler should be configured in either
withNavigationErrorHandlerwithprovideRouteror theerrorHandlerproperty in the extra options of
RouterModule.forRoot. In addition,the error handler cannot be used to change the return value of the
router navigation promise or prevent it from rejecting. Instead, if you
want to prevent the promise from rejecting, use
resolveNavigationPromiseOnError.Resolveinterface now includesRedirectCommand.core
router
routerOutletDatainput toRouterOutletdirective (#57051)v18.2.2Compare Source
core
http
router
upgrade
v18.2.1Compare Source
core
fakeAsync(#56932)migrations
v18.2.0Compare Source
Breaking Changes
zone.js
fakeAsyncwill now flush pending timers at the end ofthe given function by default. To opt-out of this, you can use
{flush: false}in options parameter offakeAsynccompiler
compiler-cli
interpolatedSignalNotInvokedextended diagnostic (#57291)core
v18.1.5Compare Source
compiler-cli
core
v18.1.4Compare Source
compiler
compiler-cli
interpolatedSignalNotInvokedextended diagnostic (#57291)language-service
v18.1.3Compare Source
compiler
compiler-cli
core
v18.1.2Compare Source
compiler
compiler-cli
core
afterNextRenderhooks return that callback value. (#57031)v18.1.1Compare Source
Configuration
📅 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 becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.