saga-query VS react-easy-state

I've heard these arguments before and I actually agree with you on a lot of them. That's why I've been trying to figure out how to make data fetching simpler in redux-saga. I've been using saga-query on personal projects for awhile now and I think it has promise. It's my response to react-query and rtk-query but from the perspective of someone who loves using redux-saga.

Redux + saga-query

I don't have all of the examples written yet in the documentation, but this idea is an async/await version of another library I experimented with saga-query which does have better examples of everything I listed above and works in virtually the same way (it just leverages redux-saga instead).

I've really enjoyed react-easy-state

For state, I love to use React Easy State.

react-easy-state was very easy.

If you want to try something a bit different with regards to state management, you can try: https://github.com/RisingStack/react-easy-state

Nope, react-easy-state is much easier: https://github.com/RisingStack/react-easy-state

I personally prefer to work with react-easy-state instead of using Redux or even the built-in state management in React.

Just started using react-easy-state in a project, and I have to say I love it. In the past, I used Redux/RTK for global state management, along with Redux Thunk or Redux Saga for side effects. In contrast, react-easy-state is easy and requires so much less boilerplate to setup and worry about. I’m fully comfortable using Redux in apps and have done it plenty of times, but I love how react-easy-state just works. It’s amazing being able to mutate the state from anywhere, inside and outside of components, and have it immediately reflected by components, without installing any plugins and having complex config files.

I am a big fan of react-easy-state, which uses proxies to automatically trigger re-renders when you mutate any state that the component depends on. It's a bit of a different way of using state management compared to typical immutable state examples, but it allows for some very straightforward code without much boilerplate around it.

The app for people to submit orders (drinks-user) is just a form and to manage state, I'm using React-easy-state