Skip to content

Commit 7c34d3d

Browse files
docs(www): update docs (#4988)
1 parent 44e17cb commit 7c34d3d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

projects/www/src/app/pages/guide/store/reducers.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -339,7 +339,7 @@ Whether your feature states are loaded eagerly or lazily depends on the needs of
339339

340340
If you have a module-based Angular application, you can still use standalone components. NgRx standalone APIs support this workflow as well.
341341

342-
For module-based apps, you have the `StoreModule.forRoot({...})` included in the `imports` array of your `AppModule`, which registers the root store for dependency injection. Standalone components look for a different injection token that can only be provided by the `provideStore({...})` function detailed above. In order to use NgRx in a standalone component, you must first add the `provideStore({...})` function the the `providers` array in your `AppModule` with the same configuration you have inside of your `forRoot({...})`. For module-based apps with standalone components, you will simply have both.
342+
For module-based apps, you have the `StoreModule.forRoot({...})` included in the `imports` array of your `AppModule`, which registers the root store for dependency injection. Standalone components look for a different injection token that can only be provided by the `provideStore({...})` function detailed above. In order to use NgRx in a standalone component, you must first add the `provideStore({...})` function to the `providers` array in your `AppModule` with the same configuration you have inside of your `forRoot({...})`. For module-based apps with standalone components, you will simply have both.
343343

344344
<ngrx-code-example header="app.module.ts">
345345

0 commit comments

Comments
 (0)