typesafe-actions VS react-query

createAction — lets you define action creators, similar to typesafe-actions. I'm a TypeScript die-hard so type safety is non-negotiable. 😆

Actually implementing a separate interface or type per action gets clunky; that's where adding libraries can help. typesafe-actions is an easy, quality library that I've used for this on a previous project. reduxjs-toolkit is even better; it provides some more structure and several useful features. As a bonus, it includes Immer built in.

Also a library reccomendation for anyone who prefers to stick with the official Redux ecosystem: https://github.com/piotrwitek/typesafe-actions. Makes the seclector/action/reducer/types store setup extremely clean and scaleable.

But as a fellow n00b there are some suggestions which will save you a crap tonne of headache (i.e. if using Redux, the typesafe-actions library gives the BEST modern framework for doing it in)

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