React Query vs "use-reducer-async" library
Hi, guys, i'm trying to do some comparasions to find the best way to handle Server State on our project.
We're a e-commerce company that we're migrating to a new stack:
From Django Template + React -> Next.js App Router
Even with RSC, we still have some client state.
Currently we have different things around from legacy code,
- Some queries useFetch custom (useEffect)
- Some queries use Redux with Saga
- Some queries use "use-reducer-async" https://github.com/dai-shi/use-reducer-async
I'm exploring introduce RQ or SWR as new alternative, but i haven't found any comparasions vs "use-reducer-async" library.
It's seems like is a good way to handle your async state, it's simple and can be broken in different Contexts or Hooks.
Can someone give me a good case for RQ or SWR, i really want to use them, but i need to present a good case for the decision.
We're a e-commerce company that we're migrating to a new stack:
From Django Template + React -> Next.js App Router
Even with RSC, we still have some client state.
Currently we have different things around from legacy code,
- Some queries useFetch custom (useEffect)
- Some queries use Redux with Saga
- Some queries use "use-reducer-async" https://github.com/dai-shi/use-reducer-async
I'm exploring introduce RQ or SWR as new alternative, but i haven't found any comparasions vs "use-reducer-async" library.
It's seems like is a good way to handle your async state, it's simple and can be broken in different Contexts or Hooks.
Can someone give me a good case for RQ or SWR, i really want to use them, but i need to present a good case for the decision.
GitHub
React useReducer with async actions. Contribute to dai-shi/use-reducer-async development by creating an account on GitHub.
