Asset Versioning

Updated 18 Sep 2026

•
What it is
- •
  giving changed application assets distinct URLs so caches can distinguish versions
•
Content hashing
- •
  unchanged content keeps the same asset URL
- •
  changed content receives a different hash-based filename
•
Deployment pattern
- •
  HTML — validate before reuse so it can point to the current assets
- •
  public assets with content-hashed URLs — long freshness lifetime and immutable
- •
  publish assets before publishing HTML that references them
- •
  retain earlier assets long enough for older sessions and lazy-loaded chunks
•
Vite
- •
  assets processed through the build graph can receive hashed names
- •
  files in public are copied as-is; do not assume they are automatically versioned.
•
Caution
- •
  purging a CDN does not purge browser caches
- •
  service-worker caches require their own update logic
- •
  deployment does not replace JavaScript already running in an open page
•
Related
- •
  HTTP Caching
•

Linked references 2