I’m searching for some insight in how Netlify invalidates browser caches on builds. I’ve seen the issue come up pretty regularly and I was hoping I could find a solution.
It’s fairly simple and I’m sure everyone has seen it. You push an update, it builds, and you’re served a cached version… Now I have no issue with Shift + Refreshing or knowing it works fine outside of my pesky local cache, but I frequently get alerted by (nontechnical) members across the broader team. I often tell them how to refresh it, but it is disheartening when a higher-up sees outdated information because the site is cached in their browser. Is there anything I can be doing to force cache invalidation? In other environments, I’ve solved it with version numbers on site assets (CSS, JS).
Any insight or ideas are appreciated. I love the platform and I have a feeling I’m just missing something