elf VS store

I have reasonable knowledge with most of other popular JS frameworks especially React. But, Angular seems quite different from DX perspective. For React, my default stage management is to use React Query for server sync and Zustand for client state. Often on Angular context I read that people recommend using NgRx and saying that it is like Redux. But I find Redux DX quite bad and I only work with it on legacy projects. So is there similar approach to managing state in Angular app? I found solutions such as: https://github.com/ngneat/query and then https://github.com/ngneat/elf. Would these make sense for Angular and are there good alternatives?

Seems that the focus is moving completely on Elf, Netanel itself removed Akita from Elf docs just 3 weeks ago: https://github.com/ngneat/elf/commit/4546d76f5adfc2c59cf188a1550c0a1d31fccd42

I like ElfJs, It's framework agnostic state management built on top of RxJS and has simple API, it works well with Angular.

The data layer consists of the data service and the repository. Data service orchestrates operations and logic while the repository is responsible for in-memory caching. I use @ngneat/elf for the repository implementation. Although it can be any other library or even fully custom code.

Alternative: https://github.com/ngneat/elf

It's still boilerplatey but a little less than NgRx. But we use Ngxs: https://ngxs.io. It's a little more complex than elf but a lot more robust in my opinion.

Hi, I switched to ngxs a while ago. (https://github.com/ngxs/store). Never been happier about this change. ngxs is written in angular way and easier to understand and it just works.

// In doing this refactoring I noticed that there is a 'bug' where the // application state is returned instead of this state slice. // This has worked this way since the beginning see: // https://github.com/ngxs/store/blame/324c667b4b7debd8eb979006c67ca0ae347d88cd/src/state-factory.ts // This needs to be fixed, but is a 'breaking' change. // I will do this fix in a subsequent PR and we can decide how to handle it.

This was recently exemplified by an RFC in the state library NGXS. In short, one of the functions published by the library was improperly typed because the type of its first argument was intended to be inferred from its contextually expected return type.