react-toastify VS react-query

React Toastify

React-Toastify is one of the most popular toast UI libraries for React or Next.js. It's easy to configure and use, but integrating it with the App router makes the configuration part a bit tricky. There is an open issue about this topic, and while you can find some solutions there, they aren't summarized. So in this article, I'll provide a summarized version of the solution to integrate React-Toastify with Next.js App router.

react-toastify: Enhance user experience with customizable toast notifications. Learn more

GitHub link: GitHub – fkhadra/react-toastify

Adding notifications to the application when a user adds/removes an item to the cart.You can use the React Toastify library to add notifications to the application.

React-toastify is a free, open-source, MIT-licensed toast package you can use to provide temporary, unobtrusive, and auto-expiring notifications in your React or refine application. You can use it with react or react-based frameworks like refine. React-toastify is a simple but powerful package.

How it diff/bettr than reactreact-toastify https://www.npmjs.com/package/react-toastify

When the Notify Me button is clicked, the onCLick event triggers the notify function which in turn renders the toast notification in the UI. Note: you must also render the component for the toast notification to work. There are configurations options that you can customize to fit into your project requirements; check out the full documentation here: Toastify Documentation

In their official example, handleError logs a message to console but it is better to return value so you can reuse in somewhere else easily later. Therefore, you can use this function instead with react-toastify or others to show notifications.

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