rx-angular VS platform

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.

NgRx is the standard library for state management in Angular applications. With NgRx v14, many of the complex APIs following the Redux pattern have been greatly simplified. For example, ActionGroups make it easier to define new actions. However, the use of the Redux pattern is by no means easy and discourages many developers.

I ran into this question question on the NgRx GitHub discussion threads which asked:

In an application that I’m working on, before Angular 16 shipped, I was using a custom StoreService to hold global application state. I’ve tried libraries like NgRx and Akita to manage global state, but found them to be way too heavy-handed for what I wanted (not saying ANYTHING negative towards these libraries; not every tool is right for every job, and the authors of these libraries would probably be the first to tell you that). This custom StoreService was created using RxJS, and looked like this:

RFC Signal Store

If you liked this, click the ❤️ so other people will see it. Follow me on Twitter and subscribe to my YouTube Channel for content on Angular, Analog, NgRx, and more!

The store can be implemented using any technology. You can either use a library like NgRx or NGXS. Another solution is to create your own store using a BehaviorSubject.

I'm using @ngrx/router-store in my Angularv5 app and I recently started running into a an error: Navigation ID X is not equal to the current navigation id Y (where X and Y are integers).

Not agree, NgRx and redux pattern helps a lot to keep the code clean, I do agree that maybe NgRx add many files and could become in boilperplate for simple staff, I think with signals this approach will change, there is already an open discussion about this https://github.com/ngrx/platform/discussions/3796

For code sample and how to architect these things : https://ngrx.io

The NgRx team and Marko Stanimirović opened a new RFC (Request for Comments) for a signal-based state management solution, SignalStore. It has a similar approach to @ngrx/component-store. The initial prototype with the API documentation is available in the NgRx SignalStore playground repo.