This reminded me of an ongoing hack that I have running in a production webapp. When I was writing it there was no easy opt-in cache busting (renaming scripts

This reminded me of an ongoing hack that I have running in a production webapp. When I was writing it there was no easy opt-in cache busting (renaming scripts at build time, or applying a static random querystring to the script requests, etc) in the minimal framework I was using and I was getting away with not using a task runner or anything like that. It was one of those "would be nice, but effort is better spent elsewhere" things, so to this day before I do releases I still bump a hardcoded version number that I pass to the templating engine for each route. I should fix that.