How Netlify removes the cache-busting chore
When you change an asset on a Netlify-hosted site — a CSS file, a script, an image — deployment, browser caching and CDN caching are not things you have to plan around. Netlify refers to the mechanism as Instant Cache Invalidation, which the company describes as part of its "rocketjuice."
The contrast is with sites hosted elsewhere. There, a linked stylesheet typically ends up carrying a manual cache-busting suffix:
<link href="https://css-tricks.com/wp-content/themes/CSS-Tricks-17/style.css?cache_bust=1594590986788" rel="stylesheet">
The ?cache_bust= characters are inserted by hand (in this case generated from a Date() call). Without them, a pushed change may not be visible until the CDN and users' browsers expire or clear their cached copy. That delay can be serious: the change may be a bug fix or a new feature, and the cached CSS can end up mismatched against HTML that isn't cached as aggressively.
Automating the workaround, or skipping it
Some sites are updated by editing that cache-busting string manually, out of convenience. More often it is automated — for example, with a hand-written Gulpfile in which part of the pipeline handles cache busting. That carries costs at every stage: writing it, maintaining it, and using it during development, and other developers have their own differing strategies for the same job.
With Netlify, the changed asset is pushed and the service detects the change and performs the cache busting itself, so the stylesheet reference needs no query string at all:
<link href="dont-even-worry-about-it.css" rel="stylesheet" />


