4 ms·

I think I've spent more time debugging errors (hitting head against wall) that come from caching than anything else. This is some combination of: content cache

I think I've spent more time debugging errors (hitting head against wall) that come from caching than anything else. This is some combination of: content cached by Cloudflare / Vercel / node server (e.g. using "node cache") / the browser (figuring out SWR, why it's working, not working, working too well, etc. etc.) / cookies/local storage / PWA settings... Aside from using browser tools like Chrome's Network and Application tabs combined with switching to different browsers and outputting a lot of console logs... what tools should I be using to get to the root of these issues?

parasti 4y ago
Just spent three hours debugging a thing that turned out to be a cache issue. I think a big part of the problem is that it's not always obvious that the resource is coming from a cache. Some proxy somewhere is serving old data, but you won't know until you actually compare the data with the origin.