Brandon Roberts

@bryanforbes yes, it should work also. `provideStore()` and includes all the previous providers and tokens, and a few new ones to support environment providers.

@bryanforbes ahh yes, that's correct because of the NgModules. You can put both in your AppModule, all the providers will get merged, so last one wins and you'll get all...

@bryanforbes most likely yes, same rule applies though with only registering the root effects once if you have any

@Jad31 sure. I'll take Store/Effects but the rest are up for grabs

Thanks everyone! I will have an example PR soon

Unless I'm mistaken on your request, then is what the `signalState` function does. https://ngrx.io/guide/signals/signal-state We wouldn't created a `computed` function that does what `signalState` does, as it might be confusing.

Would this be a breaking change?

We should update the `ng-packgr` dependency to the 18.0.0-next.x release also

@tom9744 Sure

That's our stance on it as well. Not everyone wants to use immer, and if they do they can provide their own wrapper around `patchState`. We discussed this also with...