A place for developers to talk about building on Farcaster.

/dev

DX Engineer | Head of Developer Relations at /pinata | Building orbiter.host | stevedylan.dev/links | opinions are my own

share more pls, was next applying its fetch cache settings on node-fetch?

Lowkey thinking about doing a write up on this whole escapade. It’s so absurd I think more people need to be aware how deep Next.js goes. 

I need to retest the scenario on v15 instead of v14 which a client was using and took us days to debug.

😅. Actually, yes they were patching next in v13 and I think early 14. But people complained then the stopped. But I wouldn't be surprised there's still isssues. There's always something weird in Nextjs

@blockbot Steward. Frames Builder. Pro Chess-er ♟️


Turns out it was patched in v15 so glad to see that 😮‍💨 

Basically they were applying cache settings to node-fetch inside SDKs and from what we could tell there was no way for a user to override it. If they wanted to use v14 with our SDK and prevent caching content we would have to make a patch to our fetch requests inside the SDK to use cache: "no-store" (which we did just to be safe). What's even more insane is that these are POST requests. It makes zero sense to cache a post request like that 🫠