platform VS taiga-ui

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.

Our team already has a stock of welcomed projects, especially in the Angular ecosystem, such as Taiga UI, ng-polymorpheus and Web APIs for Angular to name a few. We take them very seriously because they are not pet projects or hobbies (although we love them as if they were). Therefore you can expect our documentation to be easy to navigate, examples to be plentiful and communication to go effortlessly.

The best component library by far in terms of default design (& not using TailwindCSS) i have encounter with is Taiga UI (its so eye-catching)

You can also check out TaigaUI https://taiga-ui.dev/ they also have an awesome component framework.

If you aren’t acquainted with Taiga and randomly stumbled upon this text, let me introduce Taiga UI — a powerful set of components for Angular, which is used in dozens of Tinkoff’s products and projects! In the following sections I will briefly unpack the overall achievements related to this multifaceted library.

https://taiga-ui.dev/ Taiga UI (free)

You could copy this service in your project: https://github.com/Tinkoff/taiga-ui/blob/main/projects/cdk/services/destroy.service.ts

There's beautiful Taiga UI library for awesome devs: https://taiga-ui.dev

Our library Taiga UI contains hundreds of useful components, directives, and services. The code maintainability is a pivotal issue for our UI Kit library. That is why we always try to write as little code as possible and look for native solutions.

1. Taiga UI