Cache-Control in development nginx.conf

[matthew-white]

@ktuite encountered an issue during local development whereby Chrome would not reload an updated .js file. The file was not reloaded even after a hard refresh. As a result, a component did not reflect the latest changes. From Chrome devtools, it looked like the .js file was not requested: it was loaded from disk cache.

Right now, our development nginx.conf only sets Cache-Control for index.html, which matches what happens in production. In production, .js filenames contain a hash, which works for cache-busting, but it looks like that isn't the case in development. Given that, I think we should consider setting Cache-Control for .js files (and probably CSS files?) in the development nginx.conf.

[matthew-white]

and probably CSS files?

I don't see CSS files in development. I think that styles are inlined in the JavaScript in development.