I'd love for version numbers to make a difference in the exported game files.

Just a suggestion. I currently have a problem where the service worker is great to give HTML5 games offline support, but trying to update a game causes all kinds of headaches when the SW doesn't want to give up its old files. I like the version numbers and the fact that you can auto-increment them, but to get around some of the service workers when you try to update a game, it would behoove us to change some of the actual file names and where index.html is pointing with the version number itself. That way the service worker would know there is an update and request the new files. Just thought I'd share a thought. Thanks! Ashley

The service worker uses an internal version number and should update predictably based on that. The SW also explicitly bypasses the cache when requesting updated resources to ensure it obtains the latest version from the server. Usually if you have a problem with it still not updating, it's because something is wrong on the server side, like a CDN that is immutably caching resources so they cannot actually be updated. Unfortunately that's outside of the service worker's control. If that is a problem and you can't figure out how to fix the server-side, then one other solution is to put the version in the URL - e.g. the first export goes to example.com/v0/index.html, the second goes to example.com/v1/index.html, and so on.