chore: update origin (#925)

Author: lacolaco

.github/workflows/build-and-test.yml

@@ -17,7 +17,7 @@ jobs:
           submodules: true
       - uses: actions/setup-node@v4
         with:
-          node-version-file: 'package.json'
+          node-version-file: '.node-version'
           cache: yarn
       - run: yarn install
       - run: yarn test
@@ -29,7 +29,7 @@ jobs:
           submodules: true
       - uses: actions/setup-node@v4
         with:
-          node-version-file: 'package.json'
+          node-version-file: '.node-version'
           cache: yarn
       - run: yarn install
       - run: yarn build
@@ -54,7 +54,7 @@ jobs:
           submodules: true
       - uses: actions/setup-node@v4
         with:
-          node-version-file: 'package.json'
+          node-version-file: '.node-version'
           cache: yarn
       - run: yarn install
       - run: yarn build

.node-version

@@ -0,0 +1 @@
+v20.13.1

aio-ja/content/errors/NG0602.md

@@ -0,0 +1,62 @@
+@name Disallowed function call inside reactive context
+@category runtime
+@shortDescription A disallowed function is called inside a reactive context
+
+@description
+A function that is not allowed to run inside a reactive context was called from within a reactive context.
+
+For example, an `effect` cannot be scheduled from within a `computed` or an actively executing effect.
+Avoid calling functions like `effect` as part of template expressions, as those execute in their own reactive context.
+
+Computed expressions are expected to be pure.
+Pure means that expression do not trigger any side effects.
+Side effects are operations like scheduling `afterRender`, creating a new `effect`, or subscribing to observables.
+
+Some operations are explicitly banned inside reactive contexts in order to avoid common pitfalls.
+As an example, using `afterRender` inside a `computed` will schedule new render hooks every time the computed expression evaluates.
+This is likely not intended and could degrade application performance.
+
+### Fixing the error
+
+This error guide is non-exhaustive.
+It captures a few common scenarios and how to address the error.
+
+#### `afterRender`
+Move the call for `afterRender` outside of the reactive context.
+
+A good place to schedule the after render hook is in the component's class constructor.
+Alternatively, use `untracked` to leave the reactive context and explicitly opt-out of this error.
+
+#### `effect`
+Move the call for `effect` outside of the reactive context.
+
+A good place to schedule an effect is in a `@Component`'s class constructor.
+
+#### `toSignal`
+Move the call for `toSignal` outside of the reactive context.
+
+```typescript
+result = computed(() => {
+  const dataSignal = toSignal(dataObservable$);
+  return doSomething(dataSignal());
+});
+```
+
+can be refactored into:
+
+```typescript
+dataSignal = toSignal(dataObservable$);
+result = computed(() => doSomething(dataSignal()));
+```
+
+Alternatively, if this is not possible, consider manually subscribing to the observable.
+
+As a last resort, use `untracked` to leave the reactive context.
+Be careful as leaving the reactive context can result in signal reads to be ignored inside `untracked`.
+
+@debugging
+
+The error message mentions the function that was unexpectedly called.
+Look for this function call in your application code.
+
+Alternatively, the stack trace in your browser will show where the function was invoked and where it's located.

aio-ja/content/errors/NG0950.md

@@ -0,0 +1,18 @@
+@name Input is required but no value is available yet.
+@category runtime
+@shortDescription A required input is accessed before a value is set.
+
+@description
+A required input was accessed but no value was bound.
+
+This can happen when a required input is accessed too early in your directive or component.
+This is commonly happening when the input is read as part of class construction.
+
+Inputs are guaranteed to be available in the `ngOnInit` lifecycle hook and afterwards.
+
+## Fixing the error
+
+Access the required input in reactive contexts.
+For example, in the template itself, inside a `computed`, or inside an effect.
+
+Alternatively, access the input inside the `ngOnInit` lifecycle hook, or later.

aio-ja/content/errors/NG0951.md

@@ -0,0 +1,23 @@
+@name Child query result is required but no value is available.
+@category runtime
+@shortDescription Required child query result was accessed before query results were calculated or query has no matches.
+
+@description
+Required child query (`contentChild.required` or `viewChild.required`) result was accessed before query results were calculated or query has no matches.
+
+This can happen in two distinct situations:
+* query results were accessed before a given query could collect results;
+* a query was executed but didn't match any nodes and has no results as a consequence.
+
+Content queries and view queries each calculate their results at different points in time:
+* `contentChild` results are available after a _host_ view (template where a directive declaring a query is used) is created;
+* `viewChild` results are available after a template of a component declaring a query is created.
+
+Accessing query results before they're available results in the error described on this page. Most notably, query results are _never_ available in a constructor of the component or directive declaring a query.
+
+## Fixing the error
+
+`contentChild` query results can be accessed in the `AfterContentChecked` lifecycle hook, or later.
+`viewChild` query results can be accessed in the `AfterViewChecked` lifecycle hook, or later.
+
+Make sure that a required query matches at least one node and has results at all. You can verify this by accessing query results in the lifecycle hooks listed above.

aio-ja/content/guide/angular-package-format.en.md

@@ -347,8 +347,8 @@ This is because the tslib version is tied to the TypeScript version used to comp
 
 ## Examples
 
-*   [@angular/core package](https://unpkg.com/browse/@angular/core@13.0.0-rc.0)
-*   [@angular/material package](https://unpkg.com/browse/@angular/material@13.0.0-rc.0)
+*   [@angular/core package](https://unpkg.com/browse/@angular/core@17.0.0/)
+*   [@angular/material package](https://unpkg.com/browse/@angular/material@17.0.0/)
 
 ## Definition of terms
 

aio-ja/content/guide/angular-package-format.md

@@ -347,8 +347,8 @@ APF v10 では、プライマリエントリポイントの直接の依存関係
 
 ## 例
 
-*   [@angular/core パッケージ](https://unpkg.com/browse/@angular/core@13.0.0-rc.0)
-*   [@angular/material パッケージ](https://unpkg.com/browse/@angular/material@13.0.0-rc.0)
+*   [@angular/core パッケージ](https://unpkg.com/browse/@angular/core@17.0.0/)
+*   [@angular/material パッケージ](https://unpkg.com/browse/@angular/material@17.0.0/)
 
 ## 用語の定義
 

aio-ja/content/guide/change-detection-zone-pollution.en.md

@@ -21,7 +21,7 @@ In the image above, there is a series of change detection calls triggered by eve
 
 ## Run tasks outside `NgZone`
 
-In such cases, you can instruct Angular to avoid calling change detection for tasks scheduled by a given piece of code using [NgZone](/guide/zone).
+In such cases, you can instruct Angular to avoid calling change detection for tasks scheduled by a given piece of code using [NgZone](/api/core/NgZone).
 
 ```ts
 import { Component, NgZone, OnInit } from '@angular/core';

aio-ja/content/guide/change-detection-zone-pollution.md

@@ -21,7 +21,7 @@ Angular DevTools を使用すると、不要な変更検知の呼び出しを見
 
 ## NgZone の外でタスクを実行
 
-このような場合、[NgZone](/guide/zone) を使って、特定のコードによってスケジュールされたタスクの変更検知を呼び出さないよう Angular に指示することができます。
+このような場合、[NgZone](/api/core/NgZone) を使って、特定のコードによってスケジュールされたタスクの変更検知を呼び出さないよう Angular に指示することができます。
 
 ```ts
 import { Component, NgZone, OnInit } from '@angular/core';

aio-ja/content/guide/component-overview.en.md

@@ -142,6 +142,20 @@ To declare the styles within the component, add a `styles` property to the `@Com
 
 The `styles` property takes an array of strings that contain the CSS rule declarations.
 
+### Creating a component manually
+
+Our recommendation is to make components standalone using the `standalone: true` flag in the `@Component` decorator. 
+
+<code-example path="component-overview/src/app/component-overview/component-overview.component.4.ts" region="standalonedeclaration"></code-example>
+
+However, in the case of working with a `NgModule` based application, the component needs to be added to the proper `@NgModule`.
+To embed a component in a module, embed it in the array of declarations found in the `@NgModule` decorator.
+
+<code-example path="component-overview/src/app/component-overview/component-overview.module.ts" region="componentmoduledeclaration"></code-example>
+
+With these steps completed, your Angular component is ready for integration and use within your application. 
+
+
 ## Next steps
 
 *   For an architectural overview of components, see [Introduction to components and templates](guide/architecture-components)