react-responsive VS react-query

There are NPM packages like react-responsive that provide custom hooks for easy usage of Media Queries:

Are people using libraries like react-responsive, using tailwind css's breakpoints, or writing plain old media queries using css.

You can try this out. Also check out React responsive.

You can use react-responsive for JS media queries. Then pass props conditionally based on the media query. Alternatively make a "responsive" boolean prop and apply styles with Tailwind's responsive helpers if the prop is true.

The responsive layouts don't have to be similar at all. With a library like https://github.com/yocontra/react-responsive you can use media queries to completely switch to different components using a HOC.

Check out: react-responsive

I have personally made use of a few different things ranging from media queries directly in whatever CSS you've written or a library like react-responsive which makes it much easier to render (or not render) specific UI based on whatever screen size your app is currently being rendered on using conditional rendering. If you're using a UI library like Material UI, it most likely already has a hook for managing the content size based on the size of the media that you can use. See Material UI: useMediaQuery.

There's this pkg that makes media queries pretty easy react-responsive

11. React Responsive

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