react-hands VS TanStack Query

Oh man I have checked out your library and loved it, and I had also made a similar library: https://github.com/javaScriptKampala/react-hands a last month or so, but now all this time I plan to rewrite all of it to better after digging more into the state management land and learning about what other big players are doing and why, one thing I still don't like about existing solutions though, they don't seem react-ish to a react developer, they seem very abstract and follow wired patterns, so now am like what if we make a library that is doing all the crazy things to manage state efficiently under the hood, but on surface behaves and has a similar pattern to useState or react hooks that to a react dev it feels so natural? And checking out your library, it seems it is what I wanted to create just with a few differences, I got some even interesting ideas on this, so how can we team up?

Does anyone think react can handle most state management issues? As today's apps are usually server data or server cache intensive than app state and hat has given more rise to libs like react query? Anyways I think react can really handle app state of 99% of the time, hence am building some state management library based on react hooks instead, the end result is a simpler and familiar thing than most of these wiredo state managers that need the dev to learn a ton of concepts, check it here: https://github.com/javaScriptKampala/react-hands and give honest feedback, first release for now by the way, don't expect too much, but much coming in next release!

To ensure that we get the best TanStack Query experience possible we are also encouraged to share feedback and participate in the discussion on GitHub, which you can check out here!

I trust you found this information beneficial. For further details, please refer to the conversation on this GitHub issue here

Tanstack - Tanstack has evolved to an entire ecosystem consisting of the famous Tanstack (or React) Query, Tanstack Table, now also Tanstack Router and Tanstack Form. It started with Tanstack Query, which adopted Nx and Nx Cloud. Zack talked about this collab with Dominik, and we also had Dominik on our Nx live stream. Now, all the above-mentioned Tanstack libs have adopted Nx, and there's more coming.

"I’m building SQLSync because I want to make client-side applications easier to build without us having to reinvent the wheel each time."

Kinda ironic no?

Anyway, since the article is also about React, I can't recommend enough React Query [1] if you don't want to worry about caching data to reduce calls to the database and managing/refreshing stale data. It simplified so much my job.

[1] https://tanstack.com/query

Combine state with data fetching with react-query This should be the second choice since you have to fetch data anyway Skip this option if you are using trpc or prefer not to use react-query

onSuccess, onError and onSettled have been removed from Queries. They haven't been touched for Mutations. Please see this RFC for motivations behind this change and what to do instead.

so cacheTime was really confusing because it seemed like "this is the amount time we cache data for", but that's not what it is. So a rename had to happen. We had some discussion on the public roadmap (https://github.com/TanStack/query/discussions/4252) about what it's gonna be. I'm usually against abbreviations, simply because there's always someone who doesn't understand what it means. But all other suggestions like inactiveCacheTime also had room for interpretation. gc is an abbreviation that is known well enough (think git gc), and it's also not an option that you will customize on a daily basis (usually once, globally).

By the way, I think that useSWR and React Query take on too much. They go too deep into the multiple application layers, making themselves no longer “non-opinionated,” and in some cases, using them becomes inconvenient. There are libraries that implement the SWR standard and do not use hooks, but there are not many of them.

TanStack Query is an open source data fetching library in React developed by Tanner Linsley. It has more than 1.7 million weekly downloads on NPM and more than 35k stars on GitHub as of August 2023.