compiler
| Commit | Description |
|---|---|
add extended diagnostic for uninvoked track function on @for blocks (#60495)
|
compiler-cli
| Commit | Description |
|---|---|
| ensure HMR works with different output module type (#60797) |
core
| Commit | Description |
|---|---|
mark toObservable as stable (#60449)
| |
| stabilize linkedSignal API (#60741) | |
| Stabilize PendingTasks Injectable (#60716) | |
| fix docs for output migration (#60764) | |
| fix ng generate @angular/core:output-migration. Fixes #58650 (#60763) | |
| Flush animations when no component has been checked (#58089) | |
| reduce total memory usage of various migration schematics (#60774) | |
run ApplicationRef.prototype.bootstrap in NgZone (#60720)
|
http
| Commit | Description |
|---|---|
| Delay stabilization until next app synchronization (#60656) |
language-service
| Commit | Description |
|---|---|
| Do not provide element completions in end tag (#60616) | |
| Ensure dollar signs are escaped in completions (#60597) |
Breaking Changes
core
- Animations are guaranteed to be flushed when Angular
runs automatic change detection or manual calls toApplicationRef.tick.
Prior to this change, animations would not be flushed in some situations
if change detection did not run on any views attached to the
application. This change can affect tests which may rely on the old
behavior, often by making assertions on DOM elements that should have
been removed but weren't because DOM removal is delayed until animations
are flushed.