@michael and I noticed several occurrences where OpenMRS Modules had to be reloaded multiple times in order for a new version of Modulus UI to load into the browser. This led to one person having trouble finding a new feature that had just been released.
We should investigate this.
Can we ensure that page-reloads never use an outdated, cached version of Modulus UI?
Could we implement a feature like Discourse has, where a user is prompted to reload the page when an update is released? (see https://meta.discourse.org/t/proposed-site-settings-triggering-refresh/12935 for more info)