query VS react-query

Angular TanQuery Repo: https://github.com/ngneat/query/

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?

what you're looking for is ngneat/query. It uses tanstack query under the hood. much like in react, you can use it for async (also called server) state management, it will not help you with managing client state (like dark/light theme toggle, ...). You still need rxjs for making API calls much like you would use the fetch api or axios in the react version. I don't think it replaces signals, you could still use signals with it (and signals support seems to be planned).

react-query

React Query: This library makes it easy to manage data in your React applications, from fetching to caching and updating data. It offers a simple, powerful, and flexible API for handling data and keeping your UI in sync with your data. https://github.com/tannerlinsley/react-query

useQuery (react-query) (+) all from above (+) even more features (-) more complex, even the examples are complex, has more aggressive defaults (re-fetching every 2s)

see here Overview

Rapini is a new tool that can generate custom React Query hooks using OpenAPI (Swagger) files.

React Query is the gold standard for using async data declaratively with hooks. I ended up needing to modify even my simple useTimer hook to work more like useQuery to take multiple keys in order to work as an inner observable for other operators.

For most situations, I would recommend using a library like React Query. It handles a lot of common data-fetching boiler plate and already accounts for this useEffect() issue. Also, it supports Suspense if you want to use that.

At this point, I want to move on to the react-query cache management library. Give a brief overview and see how you can improve your developer experience with cache using this library.

There isn't the "service" concept in React. If you need to send off data you can just do so with fetch. If you need to load data and cache it so it can be used across components and unmounts, then something like react-query is what I'd recommend. But it's basically a combination of React Context, useEffect, and useState to manage the cache and lifecycle of a request.

react-query is pretty neat too. I default to that for most projects unless it's something unusual