Is Tanstack Query needed when using Next Route Handlers?
Basically what it says. To my understanding a Route Handler is basically a custom built endpoint that receives a
With that in mind, if I'm fetching data on the client, would something like Tanstack Query still be relevant / provided any significant value? I know the Route Handlers already include caching and revalidation, as does TQ, but I'm not sure if TQ provides anything further that makes it worth including.
Given the versatile nature of TQ and the sheer number of features, I imagine so, but wanted to check they weren't already covered by Next.
Request and returns a Response. Standard REST-ful stuff really.With that in mind, if I'm fetching data on the client, would something like Tanstack Query still be relevant / provided any significant value? I know the Route Handlers already include caching and revalidation, as does TQ, but I'm not sure if TQ provides anything further that makes it worth including.
Given the versatile nature of TQ and the sheer number of features, I imagine so, but wanted to check they weren't already covered by Next.
Create custom request handlers for a given route using the Web's Request and Response APIs.
