Bump @angular/compiler from 14.2.2 to 18.2.3

[dependabot[bot]]

Bumps @angular/compiler from 14.2.2 to 18.2.3.

Release notes

Sourced from @​angular/compiler's releases.

v18.2.3

18.2.3 (2024-09-04)

http

Commit	Description
	Dynamicaly call the global fetch implementation (#57531)

v18.2.2

18.2.2 (2024-08-28)

core

Commit	Description
	avoid leaking memory if component throws during creation (#57546)
	Do not bubble capture events. (#57476)

http

Commit	Description
	Dynamicaly call the global fetch implementation (#57531)

router

Commit	Description
	Do not unnecessarily run matcher twice on route matching (#57530)

upgrade

Commit	Description
	Address Trusted Types violations in @​angular/upgrade (#57454)

v18.2.1

18.2.1 (2024-08-22)

core

Commit	Description
	Allow zoneless scheduler to run inside fakeAsync (#56932)
	handle hydration of components that project content conditionally (#57383)

migrations

Commit	Description
	account for members with doc strings and no modifiers (#57389)
	avoid migrating route component in tests (#57317)
	preserve type when using inject decorator (#57389)

v18.2.0

18.2.0 (2024-08-14)

compiler

Commit	Description

... (truncated)

Changelog

Sourced from @​angular/compiler's changelog.

18.2.3 (2024-09-04)

http

Commit	Type	Description
de68e049e4	fix	Dynamicaly call the global fetch implementation (#57531)

19.0.0-next.2 (2024-08-28)

Breaking Changes

core

• Render default fallback with empty projectableNodes.

  When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.

  For example:

  // The first ng-content will render the default fallback content if present
  createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
  // To prevent projecting the default fallback content:
  createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });
  

• 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 to fakeAsync and can be affected by tick or flush.

elements

• as part of switching away from custom CD behavior to the 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

Commit	Type	Description
50f08e6c4bf	feat	automatically use sizes auto in NgOptimizedImage (#57479)

compiler-cli

Commit	Type	Description
4716c3b9660	perf	reduce duplicate component style resolution (#57502)

core

Commit	Type	Description
a3cdbfe87f5	fix	avoid leaking memory if component throws during creation (#57546)

... (truncated)

Commits

• 4f8c406 refactor(compiler): extend directive mock to avoid failing at matching logic ...
• 76ec60d refactor(compiler): ensure context is always provided for WhitespaceVisitor...
• 7bfe817 refactor(compiler): add i18nPreserveWhitespaceForLegacyExtraction (#56507)
• b30bc45 refactor(compiler): create an internal util method to detect matching directi...
• d9d68e7 fix(compiler): reduce chance of conflicts between generated factory and local...
• d73a374 Revert "fix(compiler): reduce chance of conflicts between generated factory a...
• 67e0940 fix(compiler): reduce chance of conflicts between generated factory and local...
• 08c5977 fix(compiler): limit the number of chained instructions (#57069)
• 9167fc8 fix(compiler): JIT mode incorrectly interpreting host directive configuration...
• 107173c fix(compiler): use strict equality for 'code' comparison (#56944)
• Additional commits viewable 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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[k8s-ci-robot]

Keywords which can automatically close issues and at(@) or hashtag(#) mentions are not allowed in commit messages.

The list of commits with invalid commit messages:

• 789ebe0 Bump @angular/compiler from 14.2.2 to 18.2.3

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

[k8s-ci-robot]

Keywords which can automatically close issues and at(@) mentions are not allowed in the title of a Pull Request.

You can edit the title by writing /retitle in a comment.

When GitHub merges a Pull Request, the title is included in the merge commit. To avoid invalid keywords in the merge commit, please edit the title of the PR. Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot] Once this PR has been reviewed and has the lgtm label, please assign puerco for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files: - **[OWNERS](https://github.com/kubernetes-sigs/release-notes/blob/master/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[k8s-ci-robot]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[netlify[bot]]

❌ Deploy Preview for kubernetes-sigs-release-notes failed. Why did it fail? →

Name	Link
🔨 Latest commit	789ebe09319d02bc66cd0f943cc0c33ada63a96e
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-release-notes/deploys/66d991b986ba2600082d20bd

[k8s-ci-robot]

@dependabot[bot]: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-release-notes-e2e	789ebe09319d02bc66cd0f943cc0c33ada63a96e	link	true	/test pull-release-notes-e2e
pull-release-notes-build-prod	789ebe09319d02bc66cd0f943cc0c33ada63a96e	link	true	/test pull-release-notes-build-prod
pull-release-notes-build-dev	789ebe09319d02bc66cd0f943cc0c33ada63a96e	link	true	/test pull-release-notes-build-dev
pull-release-notes-test	789ebe09319d02bc66cd0f943cc0c33ada63a96e	link	true	/test pull-release-notes-test

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

[dependabot[bot]]

Superseded by #661.