mini-rx-store VS rx-angular

Framework-agnostic code: Although MiniRx Signal Store is an Angular library, your state management code is almost framework-agnostic. Signals are an internal implementation detail of the Signal Store. Therefore, you can easily refactor your state management layer to the original (RxJS-based) MiniRx Store and use it in whatever framework you want (e.g. Svelte).

The MiniRx Signal Store API is documented in the README.

MiniRx Store

It is based on the same great concept of the original MiniRx Store which was based on RxJS (see the docs here: https://mini-rx.io/).

See the FeatureStore source here.

NgRx and the Redux pattern are great for managing state at a large scale. However, almost every application contains also features that require only a simple form of state management. Then the Redux pattern with its actions and reducers quickly feels like overkill. I wanted a state management solution which looks and feels a lot like NgRx, but it has to support simple state managment too. It was time to create MiniRx Store:

RFC: @rx-angular/state/signals - extended signal and new eventEmitter

It has been a while now since the Angular team has been exploring (way more than we can think) alternative reactivity models and looking for something that lies between the extremes of naive Zone.js (i.e. Zone.js without OnPush) and Zoneless Angular combined with special pipes & directives like those provided by RxAngular.

I would recommend exploring https://github.com/rx-angular/rx-angular. Contributors did a huge research about using Angular to get the best results.

It also includes RxAngular, a toolset focused on runtime performance and template rendering, and taiga-ui, an UI component library.

There is another reason not to use async pipes. If you provide 'noop' zone, async pipes will stop working. In my experience it's better to start without zones if you know that performance might be a problem in the future. Working without zones has more benefits https://github.com/rx-angular/rx-angular/blob/main/docs/general/zone/why-zone-less.md Here is the list.

Another cool lib which goes into the same direction as NgRx Component Store: https://github.com/rx-angular/rx-angular/blob/master/libs/state/README.md

Here are some examples: https://github.com/rx-angular/rx-angular/blob/master/libs/state/docs/usage.md

We also added listings using the same pattern. This is the first time we used *rxLet. It really makes working with all Observable in the templates easier do check it out. It allows you four states for an observable suspense, error. complete so that you can handle each one of them separately and gets rid of the *ngIf with async pipe. Like if you want to display something else while loading and error is a big disadvantage of the async pipe when used with an api.