Designer service worker caching causes NOS version discrepancy between Modeler and Designer

There have been several reports of users experiencing different NOS versions (can be checked on the header) between Modeler and Designer. Usually, Modeler shows the latest release that is supposed to be available in production, while Designer can show a much older version. When logging into connect through an incognito browser window, both versions will now match the version that is expected.

This is very likely tied to the current implementation of the Service Worker in Designer, which caches resources somewhat aggressively. The goal is to review this caching strategy and perform the changes so that this problem no longer occurs.

Notes:

• The SW settings on the webpack.config.js (might be useful).
• An hash can be added (in build time) to each file URL to force the service worker to reload the resources. This hash can be based on the version itself, ensuring that the cache is maintained in the same version but it's automatically invalidated when a new version of NOS is available.

GOAL
Investigate in a timeboxed way how to reproduce and experiment with webpack settings.
Create new tickets for the fixe(s) to land.