I’d love to hear feedback about Next / Vercel / v0 / AI SDK etc from this part of the world.

We proudly host and power some amazing crypto projects on our platform and always looking to get better.

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

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

Immutable hashed assets should always send immutable cache control headers. If you’re using a custom CDN you need to handle purging etc for pages that set cache-control. On Vercel like you said we do this automatically and we don’t recommend putting other CDNs in front as it causes cache coherence issues.