Lars Gyrup Brink Nielsen

Thank you for your syggestion, @fleish80. The serializer is mostly based on that of NgRx Router Store, meaning this feature must not be supported by that library. I would be...

I'm currently working on the [RouterHistoryStore](https://github.com/ngworker/router-component-store/pull/302). Seems like this feature request could be more related to that than to the RouterStore. @fleish80, please send use cases for router state usage.

The router state isn't part of [ActivatedRouteSnapshot](https://angular.io/api/router/ActivatedRouteSnapshot) so it's not available to the route serializer.

Related to https://github.com/ngworker/router-component-store/issues/260.

@yjaaidi I hope so, but: 1. That's what they said more than 2 years ago. 2. It's still in the *Future* section of the Angular roadmap which means that: 1....

That being said, I noted my early thoughts on this issue in "[Angular Revisited: Tree-shakable components and optional NgModules](https://dev.to/this-is-angular/angular-revisited-tree-shakable-components-and-optional-ngmodules-36d2)".

@magicmatatjahu components already work like that. This is known as component-level provider scope and the element injector. There was some work to create a more advanced node injector a few...

Do you mean so that `` doesn't get rendered in the DOM?

My mistake, I meant to ask whether you thought that `` shouldn't be rendered.

I experience similar issues when mixing the classic NgRx state APIs with the standalone NgRx state APIs. In [my minimal reproducible example](https://stackblitz.com/edit/stackblitz-starters-gpqpym?file=src%2Fapp%2Fbooks%2Fbooks.module.ts) we see that replacing `StoreModule.forFeature` with `provideState` or...