Pigeon VS react-query

Pigeon is a library that comes pretty close to what I had in mind as it is even inspired by React Query, however, it still seems a bit unfinished and the project might even be more or less dead already, so I'm a bit worried building my app around it.

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.

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.

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

Zodios also has some React Hooks. Behind the scene, Zodios is using react-query. You can also use your alias for hooks. They will be automatically prefixed with use. For example, alias getUsers can be used with useGetUsers hook.

tRPC is a built on top of react-query, which is a package for fetching, caching, and updating data without the need of any global state. We are also using zod for schema and input validations. You can also use other validation libraries like yup, Superstruct, etc. Read more.

I've written a fair amount about combining Storybook (SB), react-query (RQ), and Mock Service Worker (MSW) (see related posts below). I finally solved another piece of the puzzle for a better developer experience: forcing RQ queries to refetch after changing a control in SB that influences a response from MSW.