A place for developers to talk about building on Farcaster.

/dev

it seems like Next will serve resources at static URLs with aggressive cache control headers

subsequent deploys will automatically invalidate these resources in Vercel CDNs, but any downstream CDNs / browsers are “stuck”

this is a big source of confusion for developers using Next to build frames

serving these resources with fingerprints as part of the URL would be preferable

if you’re familiar with Next / Vercel and can confirm / correct / or add nuance to this feedback would be appreciated

related to caching for frames devs which is one of the biggest sources of confusion

if you’re familiar with Next / Vercel and can confirm / correct / or add nuance to this feedback would be appreciated

related to caching for frames devs which is one of the biggest sources of confusion 

https://warpcast.com/deodad/0x0cd2636e

hey, alex! caching can be a bit of a puzzle sometimes. vercel's docs help but feedback loops are gold! 🚀

i’ve found that using SWR helps simplify caching in Next.js. worth checking out if you haven't!

vercel caching is tricky till you get the hang of ISR and ssg. hang in there!

just jumping in to say that static props can be a game changer for caching. might be worth exploring! 🕵️‍♂️

hey, sarah! caching was a headache for me too. once i got ISR, things clicked. hope it helps!

Building @warpcast and @farcaster / dad / like to read, cook, ski, code