build: update cross-repo angular dependencies to v21 #78
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:
^20.2.0
->^21.0.0-next
21.0.0-next.5
->21.0.0-next.6
^20.2.0
->^21.0.0-next
21.0.0-next.5
->21.0.0-next.6
^20.2.0
->^21.0.0-next
21.0.0-next.5
->21.0.0-next.6
^20.2.0
->^21.0.0-next
21.0.0-next.5
->21.0.0-next.6
^20.2.0
->^21.0.0-next
21.0.0-next.5
->21.0.0-next.6
^20.2.0
->^21.0.0-next
21.0.0-next.5
->21.0.0-next.6
^20.2.0
->^21.0.0-next
21.0.0-next.5
->21.0.0-next.6
^20.2.0
->^21.0.0-next
21.0.0-next.5
->21.0.0-next.6
^20.2.0
->^21.0.0-next
^20.2.0
->^21.0.0-next
21.0.0-next.5
->21.0.0-next.6
^20.2.0
->^21.0.0-next
21.0.0-next.5
->21.0.0-next.6
21.0.0-next.5
->21.0.0-next.6
^20.2.0
->^21.0.0-next
21.0.0-next.5
->21.0.0-next.6
Release Notes
angular/angular (@angular/animations)
v21.0.0-next.6
Compare Source
Breaking Changes
elements
Fix signal input getter behavior in custom elements.
Before this change, signal inputs in custom elements required function calls to access their values (
elementRef.newInput()
), while decorator inputs were accessed directly (elementRef.oldInput
). This inconsistency caused confusion and typing difficulties.The getter behavior has been standardized so signal inputs can now be accessed directly, matching the behavior of decorator inputs:
Before:
elementRef.oldInput
elementRef.newInput()
After:
elementRef.oldInput
elementRef.newInput
common
compiler
core
elements
migrations
v21.0.0-next.5
Compare Source
common
compiler-cli
core
Resource.hasValue()
(#63994)animate.leave
(#63921)forms
FormResetEvent
when resetting control (#64024)migrations
v21.0.0-next.4
Compare Source
Breaking Changes
common
ngComponentOutletContent
is now of typeNode[][] | undefined
instead ofany[][] | undefined
.core
provideZoneChangeDetection
while also removing ZoneJS polyfills will no longer result in the
internal scheduler being disabled. All Angular applications now
consistenly use the same scheduler, and those with the Zone change detection
provider include additional automatic scheduling behaviors based on
NgZone stabilization.
for ZoneJS-based change detection by default. Add
provideZoneChangeDetection
to the providers of yourbootstrapApplication
function or yourAppModule
(if usingbootstrapModule
). This provider addition will be covered by anautomated migration.
moduleId
was removed fromComponent
metadata.interpolation
option on Components has been removed. Only the default{{ ... }}
is now supported.common
ngComponentOutletContent
(#63674)compiler
aria-invalid
(#63748)compiler-cli
core
moduleId
from Component metadata (#63482)interpolation
option on Components. (#63474)forms
migrations
v21.0.0-next.3
Compare Source
Breaking Changes
compiler-cli
"typeCheckHostBindings": false
in theangularCompilerOptions
section of your tsconfig.core
The server-side bootstrapping process has been changed to eliminate the reliance on a global platform injector.
Before:
After:
A schematic is provided to automatically update
main.server.ts
files to pass theBootstrapContext
to thebootstrapApplication
call.In addition,
getPlatform()
anddestroyPlatform()
will now returnnull
and be a no-op respectively when running in a server environment.compiler-cli
core
BootstrapContext
for improved server bootstrapping (#63562)migrations
v21.0.0-next.2
Compare Source
Breaking Changes
common
TestBed
now provides a fakePlatformLocation
implementation that supports the Navigation API. This may break some
tests, though we have not observed any failures internally. You can revert to the
old default for
TestBed
by providing theMockPlatformLocation
from@angular/common/testing
in your providers:{provide: PlatformLocation, useClass: MockPlatformLocation}
core
provideZoneChangeDetection
in theTestBed providers would previously prevent
TestBed
from rethrowingerrors as it should. Errors in the test will now be rethrown, regardless
of the usage of
provideZoneChangeDetection
. Tests should be adjusted toprevent or account for these errors. As in previous major versions,
this behavior can be disabled with
rethrowApplicationErrors: false
inconfigureTestingModule
as a last resort.ignoreChangesOutsideZone
is no longer available as anoption for configuring ZoneJS change detection behavior.
platform-browser
ApplicationConfig
export from@angular/platform-browser
has been removed.Please import
ApplicationConfig
from@angular/core
instead.router
microtasks to complete. Tests have been found to often be highly
dependent on the exact timing of navigation completions with respect to
the microtask queue. The most common fix for tests is to ensure all
navigations have been completed before making assertions. On rare
occasions, this can also affect production applications. This can be
caused by multiple subscriptions to router state throughout the application,
both of which trigger navigations that happened to not conflict with the
previous timing.
upgrade
UpgradeAdapter
is no longer available. Useupgrade/static
insteadcommon
compiler
core
rxResource
stream
threw before returning anObservable
(#63342)forms
http
platform-browser
ApplicationConfig
export (#63529)platform-server
router
upgrade
v21.0.0-next.1
Compare Source
Breaking Changes
common
forms
common
ngModuleFactory
input ofNgComponentOutlet
(#62838)compiler
core
Configuration
📅 Schedule: Branch creation - Every 2 hours, between 12:00 AM and 10:59 PM ( * 0-22/2 * * * ) in timezone America/Tijuana, 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 has been generated by Renovate Bot.