Make your life easier with React Query DevTools

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
Search for a command to run...

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
No comments yet. Be the first to comment.
Most of you know me for my consistency, a golden arrow in my blog series. I've written 1000 articles in 1008 days! Almost an article a day, and my honeymoon was the only holiday I ever took. I'm super proud of this achievement; it has been a fantasti...

It's not the first time I'll be talking about community. I think it's an essential aspect of any successful tool. This shows in my previous explorations of Astro, Medusa, and now Vendure as well. All these products thrive in a super open, welcoming, ...

The cool part about Vendure is how easy it is to set up and how abstract each layer is. Basically, we get the following elements: External database Server Worker Admin UI Frontend While this is amazing, it also brings a bit of complexity when it co...

The previous article looked at customizing Vendure on a data and process level. In this article, we'll look at customizing emails, as they are often a big part of a webshop system. We'll be looking at two different layers of customization for customi...

Even though Vendure is a pretty significant project out of the box, in some cases, we might want to go in and modify some elements to work to our specific use case. In this article, I'll take a high-level look at some elements we can customize within...

When it comes to using React Query and especially the more advanced topics, it can be pretty hard to debug what's going on.
Or sometimes, you just want to invalidate a query to see if everything works fine quickly.
That's exactly where React Query DevTools come in handy 🥳.
This is what it looks like when enabled:

If you want to use the DevTools, installing them in your main app wrapper is recommended. This way, they will be visible everywhere.
And don't worry, by default, they will only show up when your env is in development mode.
Open up your App.js file and import the DevTools.
import {ReactQueryDevtools} from 'react-query/devtools';
To import it, we should place it inside the QueryClientProvider block like so:
function App() {
return (
<QueryClientProvider client={queryClient}>
# Your app components
<ReactQueryDevtools />
</QueryClientProvider>
);
}
For this mode, we can pass the following optional properties.
initialIsOpen: You can set this to true if you want it to default show as openposition: Can be one of the following: top-left, top-right, bottom-left, bottom-right, and it determines the position of the React Query logo.Then we get some options that can be used to extend default styles or click handlers.
All of these can be used to override defaults like: className, style and onClick where applicable:
panelPropscloseButtonPropstoggleButtonPropsAlternatively you can render it as a plain component when used in embedded mode:
import {ReactQueryDevtoolsPanel} from 'react-query/devtools';
function App() {
return (
<QueryClientProvider client={queryClient}>
<ReactQueryDevtoolsPanel />
</QueryClientProvider>
);
}
Once you spool up your application with the DevTools setup, you can quickly keep track of all the fired queries.
By clicking on one of them, you get to see a lot of information for this query.
And you can quickly choose any of the following actions:

Trust me. React Query DevTools can make your life a lot easier. Knowing when a query is refetched, what data it has, or how many times it retried fetching it is such a win.
Thank you for reading my blog. Feel free to subscribe to my email newsletter and connect on Facebook or Twitter