ng-simple-state VS mini-rx-store

Ok, I understod. I use it just for retrive the full current state (https://github.com/nigrosimone/ng-simple-state/blob/main/projects/ng-simple-state/src/lib/ng-simple-state-base-store.ts#L119) and change the state with the provided partial state (https://github.com/nigrosimone/ng-simple-state/blob/main/projects/ng-simple-state/src/lib/ng-simple-state-base-store.ts#L125) .

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: