Cache Invalidation

[zackify]

Sorry if this has been asked before, but I'm trying to figure out the best way to push new releases and have the service worker be updated.

Right now, I upload all of webpack's output to S3 and then serve it through cloudfront. All outputted files have a hash in front of them, except the sw is always the same filename.

Should I simply make it so that the serviceworker has a hashed filename as well, or make it so that it is never cached so that any page load grabs the latest version of it? I hope this makes sense.

[NekR]

Hi, @zackify!

Short version:
Never cache SW file. Don't change its name, e.g. don't hash it.

Long version:
#127 -- You'll need to read whole thread to understand all the details.

:-)

[NekR]

(I hope that's correct thread, I believe it is)

[zackify]

Yes, I have this working perfectly. On AWS I never cache it, and auto update every two minutes and reload my app. Btw this is super fast on the reload since it's after the new worker caches everything! Love this plugin :)

[NekR]

Love this plugin :)

😎

[ndbroadbent]

@NekR Thanks for the explanations here and in #127. It makes sense why you don't want to add a hash to the service worker JS filename.

I'm still going to cache this file with Cloudflare, but I'm just going to purge the Cloudflare cache after uploading to S3. I already do this with my index.html and other HTML files.

[NekR]

@ndbroadbent that's probably okay, I'm not sure actually. Let us know if works or not for you 👍