Cache response from CMS in development

[amber nova]

Hi,
I'm trying to reduce the number of API calls to my CMS when in development, currently each save and refresh grabs fresh data using fetch. It looks as though the docs say fetch calls are automatically cached, but if I test this by updating the CMS, when I refresh fresh data is fetched.

Does the development server behave differently to production?

Gpt4:
https://discord.com/channels/752553802359505017/1101775561396850718

this is my fetch function:

export const newFetch = async(groq:string) => {
  const url = `https://${projectId}.api.sanity.io/v${apiVersion}/data/query/${dataset}?query=${encodeURIComponent(groq)}`
  return await fetch(url,{
    headers: {
      "Authorization": `Bearer ${process.env.SANITY_API_TOKEN}`,
    }
  }).then(res => res.json())
}

[amber nova]

Ok... something seems odd. Found a demo by vercel and recreated it, and the data doesnt cache:
https://www.youtube.com/watch?v=gSSsZReIFRk?t=618

[amber nova]

Ok, looks like it doesnt work in 13.3.2 but canary is ok 🙏

[tranquil ferry]

Hey just found ur post, im actually looking into this awell atm and it doesnt seem to get cached, did you find another method for it?

[amber nova]

Hey, only just read this, caching works for me now on 13.4, are you still having trouble?

[tranquil ferry]

Hmm it did not work for me because of the reason it has Authorization and its a GET