Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Bump @angular/compiler from 18.2.12 to 19.0.0 in /web_embedding/ng-fl…
…utter (#2494) â� ï¸� **Dependabot is rebasing this PR** â� ï¸� Rebasing might not happen immediately, so don't worry if this takes some time. Note: if you make any changes to this PR yourself, they will take precedence over the rebase. --- Bumps [@angular/compiler](https://github.com/angular/angular/tree/HEAD/packages/compiler) from 18.2.12 to 19.0.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/angular/angular/releases"><code>@â��angular/compiler</code>'s releases</a>.</em></p> <blockquote> <h2>v19.0.0</h2> <h1>19.0.0 (2024-11-19)</h1> <p>Explore Angular v19 with a blog post from the Angular team: <a href="https://blog.angular.dev/meet-angular-v19-7b29dfd05b84">https://blog.angular.dev/meet-angular-v19-7b29dfd05b84</a></p> <h2>Breaking Changes</h2> <h3>compiler</h3> <ul> <li><code>this.foo</code> property reads no longer refer to template context variables. If you intended to read the template variable, do not use <code>this.</code>.</li> </ul> <h3>core</h3> <ul> <li> <p>Angular directives, components and pipes are now standalone by default.</p> <ul> <li>Specify <code>standalone: false</code> for declarations that are currently declared in <code>@NgModule</code>s.</li> <li><code>ng update</code> for v19 will take care of this automatically.</li> </ul> </li> <li> <p>TypeScript versions less than 5.5 are no longer supported.</p> </li> <li> <p>Timing changes for <code>effect</code> API (in developer preview):</p> <ul> <li> <p>effects which are triggered outside of change detection run as part of the change detection process instead of as a microtask. Depending on the specifics of application/test setup, this can result in them executing earlier or later (or requiring additional test steps to trigger; see below examples).</p> </li> <li> <p>effects which are triggered during change detection (e.g. by input signals) run <em>earlier</em>, before the component's template.</p> </li> </ul> </li> <li> <p><code>ExperimentalPendingTasks</code> has been renamed to <code>PendingTasks</code>.</p> </li> <li> <p>The <code>autoDetect</code> feature of <code>ComponentFixture</code> will now attach the fixture to the <code>ApplicationRef</code>. As a result, errors during automatic change detection of the fixture be reported to the <code>ErrorHandler</code>. This change may cause custom error handlers to observe new failures that were previously unreported.</p> </li> <li> <p><code>createComponent</code> will now render default fallback with empty <code>projectableNodes</code>.</p> <ul> <li>When passing an empty array to <code>projectableNodes</code> in the <code>createComponent</code> API, the default fallback content of the <code>ng-content</code> will be rendered if present. To prevent rendering the default content, pass <code>document.createTextNode('')</code> as a <code>projectableNode</code>.</li> </ul> <pre lang="ts"><code>// The first ng-content will render the default fallback content if present createComponent(MyComponent. { projectableNodes: [[], [secondNode]] }); <p>// To prevent projecting the default fallback content: createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });</p> <p></code></pre></p> </li> <li> <p>Errors that are thrown during <code>ApplicationRef.tick</code> will now be rethrown when using <code>TestBed</code>. These errors should be resolved by ensuring the test environment is set up correctly to complete change detection successfully. There are two alternatives to catch the errors:</p> <ul> <li>Instead of waiting for automatic change detection to happen, trigger</li> </ul> </li> </ul> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/angular/angular/blob/main/CHANGELOG.md"><code>@â��angular/compiler</code>'s changelog</a>.</em></p> <blockquote> <h1>19.0.0 (2024-11-19)</h1> <p>Blog post: <a href="https://blog.angular.dev/meet-angular-v19-7b29dfd05b84">https://blog.angular.dev/meet-angular-v19-7b29dfd05b84</a></p> <h2>Breaking Changes</h2> <h3>compiler</h3> <ul> <li><code>this.foo</code> property reads no longer refer to template context variables. If you intended to read the template variable, do not use <code>this.</code>.</li> </ul> <h3>core</h3> <ul> <li> <p>Angular directives, components and pipes are now standalone by default.</p> <ul> <li>Specify <code>standalone: false</code> for declarations that are currently declared in <code>@NgModule</code>s.</li> <li><code>ng update</code> for v19 will take care of this automatically.</li> </ul> </li> <li> <p>TypeScript versions less than 5.5 are no longer supported.</p> </li> <li> <p>Timing changes for <code>effect</code> API (in developer preview):</p> <ul> <li> <p>effects which are triggered outside of change detection run as part of the change detection process instead of as a microtask. Depending on the specifics of application/test setup, this can result in them executing earlier or later (or requiring additional test steps to trigger; see below examples).</p> </li> <li> <p>effects which are triggered during change detection (e.g. by input signals) run <em>earlier</em>, before the component's template.</p> </li> </ul> </li> <li> <p><code>ExperimentalPendingTasks</code> has been renamed to <code>PendingTasks</code>.</p> </li> <li> <p>The <code>autoDetect</code> feature of <code>ComponentFixture</code> will now attach the fixture to the <code>ApplicationRef</code>. As a result, errors during automatic change detection of the fixture be reported to the <code>ErrorHandler</code>. This change may cause custom error handlers to observe new failures that were previously unreported.</p> </li> <li> <p><code>createComponent</code> will now render default fallback with empty <code>projectableNodes</code>.</p> <ul> <li>When passing an empty array to <code>projectableNodes</code> in the <code>createComponent</code> API, the default fallback content of the <code>ng-content</code> will be rendered if present. To prevent rendering the default content, pass <code>document.createTextNode('')</code> as a <code>projectableNode</code>.</li> </ul> <pre lang="ts"><code>// The first ng-content will render the default fallback content if present createComponent(MyComponent. { projectableNodes: [[], [secondNode]] }); <p>// To prevent projecting the default fallback content: createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });</p> <p></code></pre></p> </li> <li> <p>Errors that are thrown during <code>ApplicationRef.tick</code> will now be rethrown when using <code>TestBed</code>. These errors should be resolved by ensuring the test environment is set up correctly to complete change detection successfully. There are two alternatives to catch the errors:</p> <ul> <li>Instead of waiting for automatic change detection to happen, trigger it synchronously and expect the error. For example, a jasmine test could write <code>expect(() => TestBed.inject(ApplicationRef).tick()).toThrow()</code></li> </ul> </li> </ul> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/angular/angular/commit/806a61b5a619d98c0226ba6a566b1562f6e16e5a"><code>806a61b</code></a> fix(compiler): fix multiline selectors (<a href="https://github.com/angular/angular/tree/HEAD/packages/compiler/issues/58681">#58681</a>)</li> <li><a href="https://github.com/angular/angular/commit/e5d3abb29842412f82a67562aceff245d493ec53"><code>e5d3abb</code></a> fix(compiler): resolve <code>:host:host-context(.foo)</code> (<a href="https://github.com/angular/angular/tree/HEAD/packages/compiler/issues/58681">#58681</a>)</li> <li><a href="https://github.com/angular/angular/commit/80f56954cecf763e36bdcfbbd592a82d693eeef7"><code>80f5695</code></a> fix(compiler): transform chained pseudo-selectors (<a href="https://github.com/angular/angular/tree/HEAD/packages/compiler/issues/58681">#58681</a>)</li> <li><a href="https://github.com/angular/angular/commit/2be161d015ce6bab0142b6e6c34a8ede6341f627"><code>2be161d</code></a> fix(compiler): fix <code>:host</code> parsing in pseudo-selectors (<a href="https://github.com/angular/angular/tree/HEAD/packages/compiler/issues/58681">#58681</a>)</li> <li><a href="https://github.com/angular/angular/commit/560282aa9b3204ad8311017905beed63072c7303"><code>560282a</code></a> fix(compiler): control flow nodes with root at the end projected incorrectly ...</li> <li><a href="https://github.com/angular/angular/commit/86d8f6bda895c6681614e4ca8fe272c5dcfbebbf"><code>86d8f6b</code></a> refactor(compiler): trigger hmr load on initialization (<a href="https://github.com/angular/angular/tree/HEAD/packages/compiler/issues/58465">#58465</a>)</li> <li><a href="https://github.com/angular/angular/commit/abd0da7265fb761deebc04e3a9d9e19ba508030f"><code>abd0da7</code></a> refactor(compiler): remove unused field from output AST (<a href="https://github.com/angular/angular/tree/HEAD/packages/compiler/issues/58444">#58444</a>)</li> <li><a href="https://github.com/angular/angular/commit/b25121ee4aba427954fef074a967b9332654be84"><code>b25121e</code></a> fix(compiler): avoid having to duplicate core environment (<a href="https://github.com/angular/angular/tree/HEAD/packages/compiler/issues/58444">#58444</a>)</li> <li><a href="https://github.com/angular/angular/commit/98804fd4beb6292f5a50ce728424fdb33c47f654"><code>98804fd</code></a> fix(compiler): add more specific matcher for hydrate never block (<a href="https://github.com/angular/angular/tree/HEAD/packages/compiler/issues/58360">#58360</a>)</li> <li><a href="https://github.com/angular/angular/commit/c79b62ced2b16710876e7696b8794edc26683343"><code>c79b62c</code></a> refactor(core): remove the standalone feature (<a href="https://github.com/angular/angular/tree/HEAD/packages/compiler/issues/58288">#58288</a>)</li> <li>Additional commits viewable in <a href="https://github.com/angular/angular/commits/19.0.0/packages/compiler">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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`. --- <details> <summary>Dependabot commands and options</summary> <br /> 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 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) </details>
- Loading branch information