Add JS cache-buster

[bensteinberg]

This is a first cut at a JS cache-buster, along the lines of our existing CSS cache-busting mechanism. It renames the CSS cache-buster to distinguish it from this one. It also corrects the branch name, which I failed to update in #647.

I think it's not necessary to handle files in build/assets/lib/, as they're versioned. TBD: should we handle the JS in the century-scale storage article? build/postcss.config.js and build/tailwind.config.js?

[rebeccacremona]

🤘 Thanks for doing this!

I think it's not necessary to handle files in build/assets/lib/, as they're versioned.

Agreed.

TBD: should we handle the JS in the century-scale storage article?

Nah. I feel like, if we make significant changes there, which seems unlikely, and we are worried about it, we could just deal with it manually.

build/postcss.config.js and build/tailwind.config.js?

Ah, good one!! I think if those change, then the CSS cache needs to be busted.

[bensteinberg]

Thanks -- I'll make a change for the Tailwind stuff.

[bensteinberg]

build/*.config.js might not be correct if we added some other JS config file at the top level, but we can cross that bridge when we get to it.