Does react-query conflict with server components in Next.js?
Next.js has a built-in Data Cache that persists the result of data fetches across incoming server requests and deployments. This is possible because Next.js extends the native fetch API to allow each request on the server to set its own persistent caching semantics.
If I just make the react-query fetcher use native fetch (not axios or something) it shouldn't conflict right?
I would love to know more about this whole thing.