graphql-request and caching about next.js HOT 4 OPEN

Hi,

The cache function from React is scoped to the current request. By definition it won't work as you expect it (as a global cache)

You need to pass the next revalidate option:

fetch(`https://...`, { next: { revalidate: 3600 } })

from next.js.

I'm not looking for a global cache like the NextJS Data Cache (what you're suggesting). I'm looking for request memoization like the React Cache.

from next.js.

Aha, yeah I had missed the bit about shallow equality on the arguments passed to cache. Though you say:

Because the cache function needs to have only primitives as parameters

But the docs you link to say:

If your arguments are not primitives (ex. objects, functions, arrays), ensure you’re passing the same object reference.

So you can in turn, use cache to memoize the creation of the init argument, see #63298 (comment) - since you can also use the cache to store a computation, it is not limited to just requests.

from next.js.

So you're suggesting to use a Map to store the init object inside so I get the same reference of the init object ?

from next.js.