build(deps-dev): Bump the angular-deps group with 11 updates

[dependabot]

Bumps the angular-deps group with 11 updates:

Package	From	To
@angular-devkit/build-angular	17.3.0	17.3.1
@angular/animations	17.3.0	17.3.1
@angular/cli	17.3.0	17.3.1
@angular/common	17.3.0	17.3.1
@angular/compiler	17.3.0	17.3.1
@angular/compiler-cli	17.3.0	17.3.1
@angular/core	17.3.0	17.3.1
@angular/forms	17.3.0	17.3.1
@angular/platform-browser	17.3.0	17.3.1
@angular/platform-browser-dynamic	17.3.0	17.3.1
@angular/router	17.3.0	17.3.1

Updates @angular-devkit/build-angular from 17.3.0 to 17.3.1

Release notes

Sourced from @​angular-devkit/build-angular's releases.

v17.3.1

17.3.1 (2024-03-20)

@​schematics/angular

Commit	Description
	improve Sass format clarity for application style option

@​angular-devkit/build-angular

Commit	Description
	only generate server directory when SSR is enabled
	typo in allowedHosts warning for unsupported vite options
	avoid transforming empty component stylesheets
	reduce build times for apps with a large number of components when utilizing esbuild-based builders

Changelog

Sourced from @​angular-devkit/build-angular's changelog.

17.3.1 (2024-03-20)

@​schematics/angular

Commit	Type	Description
198ca9afc	fix	improve Sass format clarity for application style option

@​angular-devkit/build-angular

Commit	Type	Description
2809971a5	fix	only generate server directory when SSR is enabled
3f601a14e	fix	typo in allowedHosts warning for unsupported vite options
79c44adac	perf	avoid transforming empty component stylesheets
cc3167f30	perf	reduce build times for apps with a large number of components when utilizing esbuild-based builders

Commits

• 7041511 release: cut the v17.3.1 release
• 198ca9a fix(@​schematics/angular): improve Sass format clarity for application style o...
• 2809971 fix(@​angular-devkit/build-angular): only generate server directory when SSR...
• 3f601a1 fix(@​angular-devkit/build-angular): typo in allowedHosts warning for unsuppor...
• cf17331 build: update ng-dev config to work with Node.js 18.19
• 79c44ad perf(@​angular-devkit/build-angular): avoid transforming empty component style...
• a6ec0bb refactor: .idea directory
• 4b72f78 refactor(@​angular-devkit/build-angular): remove unused imported symbol
• cc3167f perf(@​angular-devkit/build-angular): reduce build times for apps with a large...
• d1637d7 refactor: remove forceConsistentCasingInFileNames from tsconfig files
• See full diff in compare view

Updates @angular/animations from 17.3.0 to 17.3.1

Release notes

Sourced from @​angular/animations's releases.

v17.3.1

17.3.1 (2024-03-20)

compiler

Commit	Description
	capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit	Description
	symbol feature detection for the compiler (#54711)

Changelog

Sourced from @​angular/animations's changelog.

17.3.1 (2024-03-20)

compiler

Commit	Type	Description
c0788200e2	fix	capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit	Type	Description
99e9474aa2	fix	symbol feature detection for the compiler (#54711)

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

• OnPush views at the root of the application need to be marked dirty for their host bindings to refresh. Previously, the host bindings were refreshed for all root views without respecting the OnPush change detection strategy.
• The ComponentFixture autoDetect feature will no longer refresh the component's host view when the component is OnPush and not marked dirty. This exposes existing issues in components which claim to be OnPush but do not correctly call markForCheck when they need to be refreshed. If this change causes test failures, the easiest fix is to change the component to ChangeDetectionStrategy.Default.
• When Angular runs change detection, it will continue to refresh any views attached to ApplicationRef that are still marked for check 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 runtime error with the NG0103 code.
• The ComponentFixture.autoDetect feature now executes change detection for the fixture within ApplicationRef.tick. This more closely 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 NgZone is now the first of either setTimeout or requestAnimationFrame. Code which relies on this timing (usually by accident) will need to be adjusted. If a callback needs to execute after change detection, we recommend afterNextRender instead of something like setTimeout.
• Newly created and views marked for check and reattached

... (truncated)

Commits

• See full diff in compare view

Updates @angular/cli from 17.3.0 to 17.3.1

Release notes

Sourced from @​angular/cli's releases.

v17.3.1

17.3.1 (2024-03-20)

@​schematics/angular

Commit	Description
	improve Sass format clarity for application style option

@​angular-devkit/build-angular

Commit	Description
	only generate server directory when SSR is enabled
	typo in allowedHosts warning for unsupported vite options
	avoid transforming empty component stylesheets
	reduce build times for apps with a large number of components when utilizing esbuild-based builders

Changelog

Sourced from @​angular/cli's changelog.

17.3.1 (2024-03-20)

@​schematics/angular

Commit	Type	Description
198ca9afc	fix	improve Sass format clarity for application style option

@​angular-devkit/build-angular

Commit	Type	Description
2809971a5	fix	only generate server directory when SSR is enabled
3f601a14e	fix	typo in allowedHosts warning for unsupported vite options
79c44adac	perf	avoid transforming empty component stylesheets
cc3167f30	perf	reduce build times for apps with a large number of components when utilizing esbuild-based builders

Commits

• 7041511 release: cut the v17.3.1 release
• 198ca9a fix(@​schematics/angular): improve Sass format clarity for application style o...
• 2809971 fix(@​angular-devkit/build-angular): only generate server directory when SSR...
• 3f601a1 fix(@​angular-devkit/build-angular): typo in allowedHosts warning for unsuppor...
• cf17331 build: update ng-dev config to work with Node.js 18.19
• 79c44ad perf(@​angular-devkit/build-angular): avoid transforming empty component style...
• a6ec0bb refactor: .idea directory
• 4b72f78 refactor(@​angular-devkit/build-angular): remove unused imported symbol
• cc3167f perf(@​angular-devkit/build-angular): reduce build times for apps with a large...
• d1637d7 refactor: remove forceConsistentCasingInFileNames from tsconfig files
• See full diff in compare view

Updates @angular/common from 17.3.0 to 17.3.1

Release notes

Sourced from @​angular/common's releases.

v17.3.1

17.3.1 (2024-03-20)

compiler

Commit	Description
	capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit	Description
	symbol feature detection for the compiler (#54711)

Changelog

Sourced from @​angular/common's changelog.

17.3.1 (2024-03-20)

compiler

Commit	Type	Description
c0788200e2	fix	capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit	Type	Description
99e9474aa2	fix	symbol feature detection for the compiler (#54711)

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

• OnPush views at the root of the application need to be marked dirty for their host bindings to refresh. Previously, the host bindings were refreshed for all root views without respecting the OnPush change detection strategy.
• The ComponentFixture autoDetect feature will no longer refresh the component's host view when the component is OnPush and not marked dirty. This exposes existing issues in components which claim to be OnPush but do not correctly call markForCheck when they need to be refreshed. If this change causes test failures, the easiest fix is to change the component to ChangeDetectionStrategy.Default.
• When Angular runs change detection, it will continue to refresh any views attached to ApplicationRef that are still marked for check 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 runtime error with the NG0103 code.
• The ComponentFixture.autoDetect feature now executes change detection for the fixture within ApplicationRef.tick. This more closely 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 NgZone is now the first of either setTimeout or requestAnimationFrame. Code which relies on this timing (usually by accident) will need to be adjusted. If a callback needs to execute after change detection, we recommend afterNextRender instead of something like setTimeout.
• Newly created and views marked for check and reattached

... (truncated)

Commits

• See full diff in compare view

Updates @angular/compiler from 17.3.0 to 17.3.1

Release notes

Sourced from @​angular/compiler's releases.

v17.3.1

17.3.1 (2024-03-20)

compiler

Commit	Description
	capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit	Description
	symbol feature detection for the compiler (#54711)

Changelog

Sourced from @​angular/compiler's changelog.

17.3.1 (2024-03-20)

compiler

Commit	Type	Description
c0788200e2	fix	capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit	Type	Description
99e9474aa2	fix	symbol feature detection for the compiler (#54711)

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

• OnPush views at the root of the application need to be marked dirty for their host bindings to refresh. Previously, the host bindings were refreshed for all root views without respecting the OnPush change detection strategy.
• The ComponentFixture autoDetect feature will no longer refresh the component's host view when the component is OnPush and not marked dirty. This exposes existing issues in components which claim to be OnPush but do not correctly call markForCheck when they need to be refreshed. If this change causes test failures, the easiest fix is to change the component to ChangeDetectionStrategy.Default.
• When Angular runs change detection, it will continue to refresh any views attached to ApplicationRef that are still marked for check 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 runtime error with the NG0103 code.
• The ComponentFixture.autoDetect feature now executes change detection for the fixture within ApplicationRef.tick. This more closely 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 NgZone is now the first of either setTimeout or requestAnimationFrame. Code which relies on this timing (usually by accident) will need to be adjusted. If a callback needs to execute after change detection, we recommend afterNextRender instead of something like setTimeout.
• Newly created and views marked for check and reattached

... (truncated)

Commits

• c078820 fix(compiler): capture data bindings for content projection purposes in block...
• See full diff in compare view

Updates @angular/compiler-cli from 17.3.0 to 17.3.1

Release notes

Sourced from @​angular/compiler-cli's releases.

v17.3.1

17.3.1 (2024-03-20)

compiler

Commit	Description
	capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit	Description
	symbol feature detection for the compiler (#54711)

Changelog

Sourced from @​angular/compiler-cli's changelog.

17.3.1 (2024-03-20)

compiler

Commit	Type	Description
c0788200e2	fix	capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit	Type	Description
99e9474aa2	fix	symbol feature detection for the compiler (#54711)

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

• OnPush views at the root of the application need to be marked dirty for their host bindings to refresh. Previously, the host bindings were refreshed for all root views without respecting the OnPush change detection strategy.
• The ComponentFixture autoDetect feature will no longer refresh the component's host view when the component is OnPush and not marked dirty. This exposes existing issues in components which claim to be OnPush but do not correctly call markForCheck when they need to be refreshed. If this change causes test failures, the easiest fix is to change the component to ChangeDetectionStrategy.Default.
• When Angular runs change detection, it will continue to refresh any views attached to ApplicationRef that are still marked for check 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 runtime error with the NG0103 code.
• The ComponentFixture.autoDetect feature now executes change detection for the fixture within ApplicationRef.tick. This more closely 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 NgZone is now the first of either setTimeout or requestAnimationFrame. Code which relies on this timing (usually by accident) will need to be adjusted. If a callback needs to execute after change detection, we recommend afterNextRender instead of something like setTimeout.
• Newly created and views marked for check and reattached

... (truncated)

Commits

• 99e9474 fix(compiler-cli): symbol feature detection for the compiler (#54711)
• 80e5a0a test(compiler-cli): add unit tests for output() JIT transform (#54841)
• c078820 fix(compiler): capture data bindings for content projection purposes in block...
• 42318e7 refactor(compiler-cli): move DelegatingPerfRecorder initialization into const...
• See full diff in compare view

Updates @angular/core from 17.3.0 to 17.3.1

Release notes

Sourced from @​angular/core's releases.

v17.3.1

17.3.1 (2024-03-20)

compiler

Commit	Description
	capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit	Description
	symbol feature detection for the compiler (#54711)

Changelog

Sourced from @​angular/core's changelog.

17.3.1 (2024-03-20)

compiler

Commit	Type	Description
c0788200e2	fix	capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit	Type	Description
99e9474aa2	fix	symbol feature detection for the compiler (#54711)

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

• OnPush views at the root of the application need to be marked dirty for their host bindings to refresh. Previously, the host bindings were refreshed for all root views without respecting the OnPush change detection strategy.
• The ComponentFixture autoDetect feature will no longer refresh the component's host view when the component is OnPush and not marked dirty. This exposes existing issues in components which claim to be OnPush but do not correctly call markForCheck when they need to be refreshed. If this change causes test failures, the easiest fix is to change the component to ChangeDetectionStrategy.Default.
• When Angular runs change detection, it will continue to refresh any views attached to ApplicationRef that are still marked for check 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 runtime error with the NG0103 code.
• The ComponentFixture.autoDetect feature now executes change detection for the fixture within ApplicationRef.tick. This more closely 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 NgZone is now the first of either setTimeout or requestAnimationFrame. Code which relies on this timing (usually by accident) will need to be adjusted. If a callback needs to execute after change detection, we recommend afterNextRender instead of something like setTimeout.
• Newly created and views marked for check and reattached

... (truncated)

Commits

• e70228a refactor(core): Add hydration missmatch on the component rather than the node...
• 1f5ab96 refactor(core): allow passing an environment injector while creating a view (...
• c078820 fix(compiler): capture data bindings for content projection purposes in block...
• See full diff in compare view

Updates @angular/forms from 17.3.0 to 17.3.1

Release notes

Sourced from @​angular/forms's releases.

v17.3.1

17.3.1 (2024-03-20)

compiler

Commit	Description
	capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit	Description
	symbol feature detection for the compiler (#54711)

Changelog

Sourced from @​angular/forms's changelog.

17.3.1 (2024-03-20)

compiler

Commit	Type	Description
c0788200e2	fix	capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit	Type	Description
99e9474aa2	fix	symbol feature detection for the compiler (#54711)

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

• OnPush views at the root of the application need to be marked dirty for their host bindings to refresh. Previously, the host bindings were refreshed for all root views without respecting the OnPush change detection strategy.
• The ComponentFixture autoDetect feature will no longer refresh the component's host view when the component is OnPush and not marked dirty. This exposes existing issues in components which claim to be OnPush but do not correctly call markForCheck when they need to be refreshed. If this change causes test failures, the easiest fix is to change the component to ChangeDetectionStrategy.Default.
• When Angular runs change detection, it will continue to refresh any views attached to ApplicationRef that are still marked for check 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 runtime error with the NG0103 code.
• The ComponentFixture.autoDetect feature now executes change detection for the fixture within ApplicationRef.tick. This more closely 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 NgZone is now the first of either setTimeout or requestAnimationFrame. Code which relies on this timing (usually by accident) will need to be adjusted. If a callback needs to execute after change detection, we recommend afterNextRender instead of something like setTimeout.
• Newly created and views marked for check and reattached

... (truncated)

Commits

• See full diff in compare view

Updates @angular/platform-browser from 17.3.0 to 17.3.1

Release notes

Sourced from @​angular/platform-browser's releases.

v17.3.1

17.3.1 (2024-03-20)

compiler

Commit	Description
	capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit	Description
	symbol feature detection for the compiler (#54711)

Changelog

Sourced from @​angular/platform-browser's changelog.

17.3.1 (2024-03-20)

compiler

Commit	Type	Description
c0788200e2	fix	capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit	Type	Description
99e9474aa2	fix	symbol feature detection for the compiler (#54711)

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

• OnPush views at the root of the application need to be marked dirty for their host bindings to refresh. Previously, the host bindings were refreshed for all root views without respecting the OnPush change detection strategy.
• The ComponentFixture autoDetect feature will no longer refresh the component's host view when the component is OnPush and not marked dirty. This exposes existing issues in components which claim to be OnPush but do not correctly call markForCheck when they need to be refreshed. If this change causes test failures, the easiest fix is to change the component to ChangeDetectionStrategy.Default.
• When Angular runs change detection, it will continue to refresh any views attached to ApplicationRef that are still marked for check 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 runtime error with the NG0103 code.
• The ComponentFixture.autoDetect feature now executes change detection for the fixture within ApplicationRef.tick. This more closely 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 NgZone is now the first of either setTimeout or requestAnimationFrame. Code which relies on this timing (usually by accident) will need to be adjusted. If a callback needs to execute after change detection, we recommend afterNextRender instead of something like setTimeout.
• Newly created and views marked for check and reattached

... (truncated)

Commits

• See full diff in compare view

Updates @angular/platform-browser-dynamic from 17.3.0 to 17.3.1

Release notes

Sourced from @​angular/platform-browser-dynamic's releases.

v17.3.1

17.3.1 (2024-03-20)

compiler

Commit	Description
	capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit	Description
	symbol feature detection for the compiler (#54711)

Changelog

Sourced from @​angular/platform-browser-dynamic's changelog.

17.3.1 (2024-03-20)

compiler

Commit	Type	Description
c0788200e2	fix	capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit	Type	Description
99e9474aa2	fix	symbol feature detection for the compiler (#54711)

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

• OnPush views at the root of the application need to be marked dirty for their host bindings to refresh. Previously, the host bindings were refreshed for all root views without respecting the OnPush change detection strategy.
• The ComponentFixture autoDetect feature will no longer refresh the component's host view when the component is OnPush and not marked dirty. This exposes existing issues in components which claim to be OnPush but do not correctly call markForCheck when they need to be refreshed. If this change causes test failures, the easiest fix is to change the component to ChangeDetectionStrategy.Default.
• When Angular runs change detection, it will continue to refresh any views attached to ApplicationRef that are still marked for check 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 runtime error with the NG0103 code.
• The ComponentFixture.autoDetect feature now executes change detection for the fixture within ApplicationRef.tick. This more closely 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 NgZone is now the first of either setTimeout or requestAnimationFrame. Code which relies on this timing (usually by accident) will need to be adjusted. If a callback needs to execute after change detection, we recommend afterNextRender instead of something like setTimeout.
• Newly created and views marked for check and reattached

... (truncated)

Commits

• See full diff in compare view

Updates @angular/router from 17.3.0 to 17.3.1

Release notes

Sourced from @​angular/router's releases.

v17.3.1

17.3.1 (2024-03-20)

compiler

Commit	Description
	capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit	Description
	symbol feature detection for the compiler (#54711)

Changelog

Sourced from @​angular/router's changelog.

17.3.1 (2024-03-20)

compiler

Commit	Type	Description
c0788200e2	fix	capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit	Type	Description
99e9474aa2	fix	symbol feature detection for the compiler (#54711)

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

• OnPush views at the root of the application need to be marked dirty for their host bindings to refresh. Previously, the host bindings were refreshed for all root views without respecting the OnPush change detection strategy.
• The ComponentFixture autoDetect feature will no longer refresh the component's host view when the component is OnPush and not marked dirty. This exposes existing issues in components which claim to be OnPush but do not correctly call markForCheck when they need to be refreshed. If this change causes test failures, the easiest fix is to change the component to ChangeDetectionStrategy.Default.
• When Angular runs change detection, it will continue to refresh any views attached to ApplicationRef that are still marked for check 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 runtime error with the NG0103 code.
• The ComponentFixture.autoDetect feature now executes change detection for the fixture within ApplicationRef.tick. This more closely 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 NgZone is now the first of either setTimeout or requestAnimationFrame. Code which relies on this timing (usually by accident) will need to be adjusted. If a callback needs to execute after change detection, we recommend afterNextRender instead of something like setTimeout.
• Newly created and views marked for check and reattached

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions