Next has gone too far with the caching. Caching should be opt-in almost always, otherwise you get all kinds of unexpected behavior. I'd rather have a slower app that works than a broken one that's fast

"with zero or minimal configuration" may have been a mistake

Making the blockchain invisible at /thirdweb

Overriding the native fetch api should have been the biggest red flag of all time ffs

Hey kids, remember: Next.js likes to cache API routes so you might be getting the same data over and over when you're not supposed to. Disable that stuff, save a life.

Welcome to the club 😎 https://warpcast.com/stevedylandev.eth/0xa0e52cfe

✳︎ design engineer/ui wizard → @ponder 
✳︎ humanist • petrolhead/gearhead
✳︎ React+SwiftUI
✳︎ bento.me/matthew

https://warpcast.com/matthewmorek/0x0b8fbd53

Caching is a debugging nightmare. 

Magic cashing is pure insomnia!