daylight: explore cache busting strategies for microfrontend files
!3997 (merged) adds some basic Cache-Control behavior for microfrontends but, as noted there:
ideally, we could setup the servers to serve put most (or all? i'm not sure how we would do this with
index.*
files?) with a query parameter likeblah.js?sha=deadbeef123123
, and allow us to actively bust the cache by changing references at deploy time. i think there's a lot to figure out about setting up a strategy like this, though. so this is here for now.
in the best case scenario, caches for both server-side rendering and on the browser side would only bust when we actually change the files; i.e. we have Cache-Control: max-age=31536000, immutable
or equivalent set, and URLs/references always change when files change.
the behavior in !3997 (merged) should hopefully be adequate to allow us defer this work in the medium term.