Checking before I go to -help -- is there a pattern for preserving old assets or implementing "skew
Checking before I go to -help -- is there a pattern for preserving old assets or implementing "skew protection" on CF Workers + Static Assets that I'm missing? It doesn't seem like there's any complete solution for this on the current version of Workers that I can find.
Context: we're running into the issue where we frequently deploy an SPA to Workers with Static Assets and users who are on stale versions of the app encounter 404s when assets lazy-load and it breaks the app., The assets have a fingerprint in them (produced by Vite) and it changes between deploys. The old assets / fingerprints are immediately invalidated on deploy (AFAICT.) This is a pure SPA that doesn't use SSR at all, there is a Workers script that proxies our API that is invoked when no asset matches; it passes API paths to the backend API service and otherwise just fetches from
Context: we're running into the issue where we frequently deploy an SPA to Workers with Static Assets and users who are on stale versions of the app encounter 404s when assets lazy-load and it breaks the app., The assets have a fingerprint in them (produced by Vite) and it changes between deploys. The old assets / fingerprints are immediately invalidated on deploy (AFAICT.) This is a pure SPA that doesn't use SSR at all, there is a Workers script that proxies our API that is invoked when no asset matches; it passes API paths to the backend API service and otherwise just fetches from
env.ASSETS
