Integrity hash can be cached incorrectly at times

[rmccue]

There's a bug with the integrity hash locally where it will be cached even though you're working on development. We should disable the cache (and just the cache) for local development.

It seems like similar problems may be occurring in production after deploys per @roborourke's findings on the test site. I'm not sure if that's related, but there might be an overlapping issue here.