feat: update origin to 4d985a179e (Angular v22.1.1) (#1197)

* chore: update origin to 4d985a179e

* fix: migrate untranslated files

* fix(docs): retranslate updated sections in src/content/guide/aria

* fix(docs): retranslate updated sections in src/content/ai

* chore(docs): reset rewritten pages to upstream English in src/content/ai

* fix(docs): retranslate updated sections in src/content/events

* fix(docs): apply upstream wording changes in src/content/events

* fix(app): translate new update-guide steps and update the cookie popup markup

* fix(app): update navigation entries and home template for v22.1

* fix(docs): apply upstream wording changes in src/content/guide/signals

* chore(docs): insert new upstream sections untranslated in src/content/guide/signals

* fix(docs): mirror upstream code and link changes in src/content/best-practices

* fix(docs): apply upstream wording changes in src/content/guide/templates

* fix(docs): retranslate updated sections in src/content/guide/templates

* fix(docs): mirror upstream code and link changes in src/content/guide/templates

* chore(docs): insert new upstream sections untranslated in src/content/guide/templates

* fix(docs): apply upstream wording changes in src/content/guide/di

* fix(docs): retranslate updated sections in src/content/guide/di

* fix(docs): apply upstream wording changes in src/content/guide/forms

* fix(docs): mirror upstream code and link changes in src/content/guide/forms

* fix(docs): apply upstream wording changes in src/content/guide/forms/signals

* fix(docs): retranslate updated sections in src/content/guide/forms/signals

* chore(docs): insert new upstream sections untranslated in src/content/guide/forms/signals

* fix(docs): apply upstream wording changes in src/content/guide/http

* fix(docs): retranslate updated sections in src/content/guide/http

* fix(docs): mirror upstream code and link changes in src/content/guide/routing

* fix(docs): apply upstream wording changes in src/content/guide/routing

* fix(docs): retranslate updated sections in src/content/guide/routing

* fix(docs): mirror upstream code and link changes in src/content/guide/testing

* fix(docs): apply upstream wording changes in src/content/guide/testing

* fix(docs): retranslate updated sections in src/content/guide/testing

* chore(docs): insert new upstream sections untranslated in src/content/guide/testing

* fix(docs): apply upstream wording changes in src/content/guide

* fix(docs): retranslate updated sections in src/content/guide

* chore(docs): insert new upstream sections untranslated in src/content/guide

* fix(docs): apply upstream wording changes in src/content/guide/animations

* fix(docs): apply upstream wording changes in src/content/introduction

* fix(docs): apply upstream wording changes in src/content/introduction/essentials

* chore(docs): insert new upstream sections untranslated in src/content/introduction/essentials

* fix(docs): retranslate updated sections in src/content/reference

* fix(docs): update roadmap for the v22.1 release

* fix(docs): mirror upstream code and link changes in src/content/reference/errors

* fix(docs): apply upstream wording changes in src/content/reference/errors

* fix(docs): retranslate updated sections in src/content/tools/cli

* fix(docs): apply upstream wording changes in src/content/tutorials/learn-angular/intro

* fix(docs): retranslate updated sections in src/content/tutorials/learn-angular/steps/19-creating-an-injectable-service

* fix(docs): apply upstream wording changes in src/content/tutorials/learn-angular/steps/25-next-steps

* fix(docs): apply upstream wording changes in src/content/tutorials/signal-forms/intro

* fix(docs): apply upstream wording changes in src/content/tutorials/signal-forms/steps/6-next-steps

* fix(docs): apply upstream wording changes in src/content/tutorials/signals/intro

* fix(docs): apply upstream wording changes in src/content/tutorials/signals/steps/11-next-steps

* fix(docs): mirror upstream code and link changes in src/content/tutorials/signals/steps/7-using-signals-with-services

* fix(docs): mirror upstream code and link changes in src/content/guide/components

* fix(docs): retranslate updated sections in src/content/guide/components

* chore(docs): insert new upstream sections untranslated in src/content/guide/components

* fix(docs): retranslate updated sections in src/content/guide/directives

* chore(docs): reset rewritten pages to upstream English in src/content/guide/directives

* fix(docs): retranslate updated API section in guide/aria/combobox

* fix(docs): add explicit anchor IDs to translated headings

Angular v22.1 adds a link validator to the API docs rendering pipeline
(validateGuideUrl). It resolves every guide link with a fragment against
the anchors the page actually exposes. Japanese headings without an
explicit {#id} generate a Japanese-text ID, so 42 links from upstream
JsDoc no longer resolved and the build failed.

Anchor IDs are derived from the English heading at the same line index.

Author: lacolaco

adev-ja/shared-docs/components/cookie-popup/cookie-popup.component.en.html

@@ -1,8 +1,16 @@
 @if (!hasAccepted()) {
   <div class="docs-cookies-popup docs-invert-mode">
-    <p>This site uses cookies from Google to deliver its services and to analyze traffic.</p>
+    <div class="docs-cookies-popup-header">
+      <img
+        class="docs-cookies-popup-angie"
+        src="assets/images/angie/greeting.svg"
+        alt=""
+        aria-hidden="true"
+      />
+      <p>This site uses cookies from Google to deliver its services and to analyze traffic.</p>
+    </div>
 
-    <div>
+    <div class="docs-cookies-popup-actions">
       <a
         href="https://policies.google.com/technologies/cookies"
         target="_blank"

adev-ja/shared-docs/components/cookie-popup/cookie-popup.component.html

@@ -1,8 +1,16 @@
 @if (!hasAccepted()) {
   <div class="docs-cookies-popup docs-invert-mode">
-    <p>このサイトでは、サービスの提供とトラフィックの分析のためにGoogleのクッキーを使用しています。</p>
+    <div class="docs-cookies-popup-header">
+      <img
+        class="docs-cookies-popup-angie"
+        src="assets/images/angie/greeting.svg"
+        alt=""
+        aria-hidden="true"
+      />
+      <p>このサイトでは、サービスの提供とトラフィックの分析のためにGoogleのクッキーを使用しています。</p>
+    </div>
 
-    <div>
+    <div class="docs-cookies-popup-actions">
       <a
         href="https://policies.google.com/technologies/cookies"
         target="_blank"

adev-ja/src/app/features/home/home.component.en.html

@@ -228,7 +228,7 @@ <h2>Want to learn more about Angular?</h2>
   <section class="learn-more-bottom-section" id="bottom">
     <div class="pattern"></div>
     <div class="content">
-      <h2>Want to learn more about Angular ?</h2>
+      <h2>Want to learn more about Angular?</h2>
       <button
         class="docs-primary-btn"
         [attr.text]="'Learn more'"

adev-ja/src/app/features/update/recommendations.en.ts

@@ -245,7 +245,7 @@ export const RECOMMENDATIONS: Step[] = [
     level: ApplicationComplexity.Basic,
     step: 'node 8',
     action:
-      'Make sure you are using [Node 8 or later](http://www.hostingadvice.com/how-to/update-node-js-latest-version/)',
+      'Make sure you are using [Node 8 or later](https://www.hostingadvice.com/how-to/update-node-js-latest-version/)',
   },
   {
     possibleIn: 600,
@@ -486,7 +486,7 @@ export const RECOMMENDATIONS: Step[] = [
     level: ApplicationComplexity.Basic,
     step: 'node 10',
     action:
-      'Make sure you are using [Node 10 or later](http://www.hostingadvice.com/how-to/update-node-js-latest-version/).',
+      'Make sure you are using [Node 10 or later](https://www.hostingadvice.com/how-to/update-node-js-latest-version/).',
   },
   {
     possibleIn: 800,
@@ -579,7 +579,7 @@ export const RECOMMENDATIONS: Step[] = [
     level: ApplicationComplexity.Basic,
     step: 'node 10.13',
     action:
-      'Make sure you are using [Node 10.13 or later](http://www.hostingadvice.com/how-to/update-node-js-latest-version/).',
+      'Make sure you are using [Node 10.13 or later](https://www.hostingadvice.com/how-to/update-node-js-latest-version/).',
   },
   {
     possibleIn: 900,
@@ -708,7 +708,7 @@ export const RECOMMENDATIONS: Step[] = [
     level: ApplicationComplexity.Advanced,
     step: 'wtf',
     action:
-      'Support for web tracing framework in Angular was deprecated in version 8. You should stop using any of the `wtf*` APIs. To do performance tracing, we recommend using [browser performance tools](https://developers.google.com/web/tools/lighthouse/audits/user-timing).',
+      'Support for web tracing framework in Angular was deprecated in version 8. You should stop using any of the `wtf*` APIs. To do performance tracing, we recommend using [browser performance tools](https://developer.chrome.com/docs/lighthouse/performance/user-timings).',
   },
   {
     possibleIn: 800,
@@ -780,7 +780,7 @@ export const RECOMMENDATIONS: Step[] = [
     level: ApplicationComplexity.Medium,
     step: '$localize',
     action:
-      "If you use [Angular's i18n support](http://angular.io/guide/i18n), you will need to begin using `@angular/localize`. Learn more about the [$localize Global Import Migration](https://v9.angular.io/guide/migration-localize).",
+      "If you use [Angular's i18n support](https://angular.io/guide/i18n), you will need to begin using `@angular/localize`. Learn more about the [$localize Global Import Migration](https://v9.angular.io/guide/migration-localize).",
   },
 
   {
@@ -981,7 +981,7 @@ export const RECOMMENDATIONS: Step[] = [
     level: ApplicationComplexity.Basic,
     step: 'v11 browser support',
     action:
-      'Support for IE9, IE10, and IE mobile has been removed. This was announced in the [v10 update](http://blog.angular.dev/version-10-of-angular-now-available-78960babd41#c357). ',
+      'Support for IE9, IE10, and IE mobile has been removed. This was announced in the [v10 update](https://blog.angular.dev/version-10-of-angular-now-available-78960babd41#c357). ',
   },
   {
     possibleIn: 1100,
@@ -1348,7 +1348,7 @@ export const RECOMMENDATIONS: Step[] = [
     level: ApplicationComplexity.Basic,
     step: 'v13 node',
     action:
-      'Make sure you are using [Node 12.20.0 or later](http://www.hostingadvice.com/how-to/update-node-js-latest-version/)',
+      'Make sure you are using [Node 12.20.0 or later](https://www.hostingadvice.com/how-to/update-node-js-latest-version/)',
   },
   {
     possibleIn: 1300,
@@ -1471,7 +1471,7 @@ export const RECOMMENDATIONS: Step[] = [
     level: ApplicationComplexity.Basic,
     step: 'v14 node',
     action:
-      'Make sure you are using [Node 14.15.0 or later](http://www.hostingadvice.com/how-to/update-node-js-latest-version/)',
+      'Make sure you are using [Node 14.15.0 or later](https://www.hostingadvice.com/how-to/update-node-js-latest-version/)',
   },
   {
     possibleIn: 1400,
@@ -2542,6 +2542,14 @@ export const RECOMMENDATIONS: Step[] = [
     possibleIn: 1900,
     step: '19.0.0-update-fakeasync-to-flush-pending-timers',
   },
+  {
+    action:
+      'Remove the `allowSignalWrites` option from `effect()` calls. The option is deprecated and no longer required, as signal writes inside effects are allowed by default.',
+    level: ApplicationComplexity.Medium,
+    necessaryAsOf: 1900,
+    possibleIn: 1900,
+    step: '19.0.0-remove-allow-signal-writes',
+  },
   {
     action:
       "In the application's project directory, run `ng update @angular/core@20 @angular/cli@20` to update your application to Angular v20.",
@@ -2781,6 +2789,15 @@ export const RECOMMENDATIONS: Step[] = [
     step: 'update @angular/material',
     action: 'Run `ng update @angular/material@21`.',
   },
+  {
+    possibleIn: 2100,
+    necessaryAsOf: 2100,
+    level: ApplicationComplexity.Medium,
+    material: true,
+    step: '21.0.0-cdk-overlay-top-layer-stacking',
+    action:
+      "CDK overlays can now render in the browser's native top layer, causing elements that previously appeared above Material overlays via `z-index` to render beneath them. You can restore the previous behavior by providing `OVERLAY_DEFAULT_CONFIG` from `@angular/cdk/overlay` with the value `{usePopover: false}`.",
+  },
   {
     possibleIn: 2100,
     necessaryAsOf: 2100,
@@ -2998,6 +3015,14 @@ export const RECOMMENDATIONS: Step[] = [
     action:
       'Angular expressions with optional chaining (`?.`) now return `undefined` instead of `null`. You can use the `$safeNavigationMigration()` magic function to revert to the previous behavior.',
   },
+  {
+    possibleIn: 2200,
+    necessaryAsOf: 2200,
+    level: ApplicationComplexity.Medium,
+    step: '22.0.0-resource-stream-synchronous-resolution',
+    action:
+      'The `stream` property on `Resource`, including `rxResource`, now resolves synchronously when the stream or observable emits synchronously. Tests that assumed asynchronous resolution may need to wait for the value immediately instead.',
+  },
   {
     possibleIn: 2200,
     necessaryAsOf: 2200,
@@ -3030,6 +3055,14 @@ export const RECOMMENDATIONS: Step[] = [
     action:
       'The `reportProgress` option in HTTP requests is deprecated. Use `reportUploadProgress` or `reportDownloadProgress` instead for more explicit control over progress reporting.',
   },
+  {
+    possibleIn: 2200,
+    necessaryAsOf: 2200,
+    level: ApplicationComplexity.Medium,
+    step: '22.0.0-deprecate-server-xhr',
+    action:
+      'XHR support in `@angular/platform-server` is deprecated and is intended to be removed in Angular 23. The underlying `xhr2` library does not safely handle redirects (e.g. it can forward `Authorization` headers on cross-origin redirects and is susceptible to DoS via redirect loops). For server-side rendering, use the default `fetch` backend instead of `withXhr()`.',
+  },
   {
     possibleIn: 2200,
     necessaryAsOf: 2200,

adev-ja/src/app/features/update/recommendations.ts

@@ -245,7 +245,7 @@ export const RECOMMENDATIONS: Step[] = [
     level: ApplicationComplexity.Basic,
     step: 'node 8',
     action:
-      '[Node 8以降](http://www.hostingadvice.com/how-to/update-node-js-latest-version/)を使用していることを確認してください。',
+      '[Node 8以降](https://www.hostingadvice.com/how-to/update-node-js-latest-version/)を使用していることを確認してください。',
   },
   {
     possibleIn: 600,
@@ -486,7 +486,7 @@ export const RECOMMENDATIONS: Step[] = [
     level: ApplicationComplexity.Basic,
     step: 'node 10',
     action:
-      '[Node 10以降](http://www.hostingadvice.com/how-to/update-node-js-latest-version/)を使用していることを確認してください。',
+      '[Node 10以降](https://www.hostingadvice.com/how-to/update-node-js-latest-version/)を使用していることを確認してください。',
   },
   {
     possibleIn: 800,
@@ -579,7 +579,7 @@ export const RECOMMENDATIONS: Step[] = [
     level: ApplicationComplexity.Basic,
     step: 'node 10.13',
     action:
-      '[Node 10.13以降](http://www.hostingadvice.com/how-to/update-node-js-latest-version/)を使用していることを確認してください。',
+      '[Node 10.13以降](https://www.hostingadvice.com/how-to/update-node-js-latest-version/)を使用していることを確認してください。',
   },
   {
     possibleIn: 900,
@@ -708,7 +708,7 @@ export const RECOMMENDATIONS: Step[] = [
     level: ApplicationComplexity.Advanced,
     step: 'wtf',
     action:
-      'AngularでのWebトレーシングフレームワークのサポートはバージョン8で非推奨になりました。`wtf*` APIの使用をやめるべきです。パフォーマンス追跡を行うには、[ブラウザのパフォーマンスツール](https://developers.google.com/web/tools/lighthouse/audits/user-timing)の使用をお勧めします。',
+      'AngularでのWebトレーシングフレームワークのサポートはバージョン8で非推奨になりました。`wtf*` APIの使用をやめるべきです。パフォーマンス追跡を行うには、[ブラウザのパフォーマンスツール](https://developer.chrome.com/docs/lighthouse/performance/user-timings)の使用をお勧めします。',
   },
   {
     possibleIn: 800,
@@ -780,7 +780,7 @@ export const RECOMMENDATIONS: Step[] = [
     level: ApplicationComplexity.Medium,
     step: '$localize',
     action:
-      '[Angularのi18nサポート](http://angular.io/guide/i18n)を使用している場合、`@angular/localize`の使用を開始する必要があります。[$localizeグローバルインポートマイグレーション](https://v9.angular.io/guide/migration-localize)について詳しくはこちらを参照してください。',
+      '[Angularのi18nサポート](https://angular.io/guide/i18n)を使用している場合、`@angular/localize`の使用を開始する必要があります。[$localizeグローバルインポートマイグレーション](https://v9.angular.io/guide/migration-localize)について詳しくはこちらを参照してください。',
   },
 
   {
@@ -981,7 +981,7 @@ export const RECOMMENDATIONS: Step[] = [
     level: ApplicationComplexity.Basic,
     step: 'v11 browser support',
     action:
-      'IE9、IE10、およびIEモバイルのサポートは削除されました。これは[v10アップデート](http://blog.angular.dev/version-10-of-angular-now-available-78960babd41#c357)で発表されました。',
+      'IE9、IE10、およびIEモバイルのサポートは削除されました。これは[v10アップデート](https://blog.angular.dev/version-10-of-angular-now-available-78960babd41#c357)で発表されました。',
   },
   {
     possibleIn: 1100,
@@ -1348,7 +1348,7 @@ export const RECOMMENDATIONS: Step[] = [
     level: ApplicationComplexity.Basic,
     step: 'v13 node',
     action:
-      '[Node 12.20.0以降](http://www.hostingadvice.com/how-to/update-node-js-latest-version/)を使用していることを確認してください。',
+      '[Node 12.20.0以降](https://www.hostingadvice.com/how-to/update-node-js-latest-version/)を使用していることを確認してください。',
   },
   {
     possibleIn: 1300,
@@ -1471,7 +1471,7 @@ export const RECOMMENDATIONS: Step[] = [
     level: ApplicationComplexity.Basic,
     step: 'v14 node',
     action:
-      '[Node 14.15.0以降](http://www.hostingadvice.com/how-to/update-node-js-latest-version/)を使用していることを確認してください。',
+      '[Node 14.15.0以降](https://www.hostingadvice.com/how-to/update-node-js-latest-version/)を使用していることを確認してください。',
   },
   {
     possibleIn: 1400,
@@ -2542,6 +2542,14 @@ export const RECOMMENDATIONS: Step[] = [
     possibleIn: 1900,
     step: '19.0.0-update-fakeasync-to-flush-pending-timers',
   },
+  {
+    action:
+      '`effect()`の呼び出しから`allowSignalWrites`オプションを削除してください。エフェクト内でのシグナルへの書き込みがデフォルトで許可されるようになったため、このオプションは非推奨となり不要になりました。',
+    level: ApplicationComplexity.Medium,
+    necessaryAsOf: 1900,
+    possibleIn: 1900,
+    step: '19.0.0-remove-allow-signal-writes',
+  },
   {
       action:
         'アプリケーションのプロジェクトディレクトリで、`ng update @angular/core@20 @angular/cli@20` を実行して、アプリケーションをAngular v20に更新します。',
@@ -2781,6 +2789,15 @@ export const RECOMMENDATIONS: Step[] = [
     step: 'update @angular/material',
     action: '`ng update @angular/material@21` を実行します。',
   },
+  {
+    possibleIn: 2100,
+    necessaryAsOf: 2100,
+    level: ApplicationComplexity.Medium,
+    material: true,
+    step: '21.0.0-cdk-overlay-top-layer-stacking',
+    action:
+      'CDKオーバーレイは、ブラウザのネイティブなトップレイヤーにレンダリングできるようになりました。これにより、以前は`z-index`によってMaterialオーバーレイの上に表示されていた要素が、その下に表示されるようになる場合があります。以前の動作に戻すには、`@angular/cdk/overlay`から`OVERLAY_DEFAULT_CONFIG`を`{usePopover: false}`という値で提供してください。',
+  },
   {
     possibleIn: 2100,
     necessaryAsOf: 2100,
@@ -2998,6 +3015,14 @@ export const RECOMMENDATIONS: Step[] = [
     action:
       'オプショナルチェイニング (`?.`) を使用した Angular の式は、`null` の代わりに `undefined` を返すようになりました。以前の動作に戻すには `$safeNavigationMigration()` マジック関数を使用できます。',
   },
+  {
+    possibleIn: 2200,
+    necessaryAsOf: 2200,
+    level: ApplicationComplexity.Medium,
+    step: '22.0.0-resource-stream-synchronous-resolution',
+    action:
+      '`rxResource`を含む`Resource`の`stream`プロパティは、ストリームやObservableが同期的にemitする場合、同期的に解決されるようになりました。非同期的な解決を前提としていたテストは、代わりに値をすぐに待つように修正する必要があるかもしれません。',
+  },
   {
     possibleIn: 2200,
     necessaryAsOf: 2200,
@@ -3030,6 +3055,14 @@ export const RECOMMENDATIONS: Step[] = [
     action:
       'HTTP リクエストの `reportProgress` オプションは非推奨になりました。進捗レポートをより明示的に制御するには、代わりに `reportUploadProgress` または `reportDownloadProgress` を使用してください。',
   },
+  {
+    possibleIn: 2200,
+    necessaryAsOf: 2200,
+    level: ApplicationComplexity.Medium,
+    step: '22.0.0-deprecate-server-xhr',
+    action:
+      '`@angular/platform-server`におけるXHRサポートは非推奨となり、Angular 23で削除される予定です。基盤となる`xhr2`ライブラリはリダイレクトを安全に処理できません（たとえば、クロスオリジンのリダイレクトで`Authorization`ヘッダーを転送してしまうことがあり、リダイレクトループによるDoSの影響を受けやすくなっています）。サーバーサイドレンダリングでは、`withXhr()`の代わりにデフォルトの`fetch`バックエンドを使用してください。',
+  },
   {
     possibleIn: 2200,
     necessaryAsOf: 2200,