A place for developers to talk about building on Farcaster.

/dev

got caught off guard by vercels data cache...

we call the hypersub smart contract to get a users remaining time via serverless function

the calls are made with viem/alchemy, which uses fetch under the hood 

I guess vercel started caching fetch requests recently? this led to subscriptions not being recognized in our app 😞

𝓵𝓲𝓿𝓲𝓷𝓰 𝓽𝓱𝓮 𝓮𝓷𝓭𝓵𝓮𝓼𝓼 𝓼𝓾𝓶𝓶𝓮𝓻 • building @buoy 🛟 • pfista.com

You should return a cache-control header from your lambda to prevent this or do a post or add a ?tm= cache bust parameter of unixtime.

How would I do that for the call that’s in my lambda? It’s a contract call through viem to an alchemy node, afaik viem doesn’t let you control the underlying fetch settings

https://rc.viem.sh/docs/clients/transports/http.html#fetchoptions-optional

and 

https://vercel.com/blog/vercel-cache-api-nextjs-cache#revalidating-components-with-cache-tags

so 
`fetchOptions: {cache: 'no-store'}`
will allow for overriding this behavior with the parameters on the http() transport from viem.