●Change8

Migrating to Angular v22.0.0-next.4

Version v22.0.0-next.4 introduces 2 breaking changes. This guide details how to update your code.

Released: 3/19/2026

2
Breaking Changes
3
Migration Steps
5
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

ChangeDetectorRef.checkNoChangesTestBed.getFixtureTestBed.getLastFixturengNoCvawithComponentInputBinding

Breaking Changes

●Issue #1

Leave animations are no longer limited to the element being removed. This may affect custom animation logic that relied on this limitation.

●Issue #2

ChangeDetectorRef.checkNoChanges was removed. In tests use fixture.detectChanges() instead.

Migration Steps

  1. 1
    If you relied on the previous scoping behavior of leave animations, review and adjust your animation logic.
  2. 2
    Replace usages of `ChangeDetectorRef.checkNoChanges` with `fixture.detectChanges()` in tests.
  3. 3
    Update usages of `TestBed.getFixture` to use `TestBed.getLastFixture`.

Release Summary

This release introduces new features like nested leave animations and support for ngNoCva, alongside several bug fixes across compiler, core, and forms. Notably, `ChangeDetectorRef.checkNoChanges` has been removed.

Need More Details?

View the full release notes and all changes for Angular v22.0.0-next.4.

View Full Changelog