Prevent mixed HTML and JavaScript versions after a site update
The practical problem
Old cached JavaScript combined with fresh HTML can create broken game states and impossible reproduction steps.
Implementation protocol
Use immutable versioned asset filenames and a controlled entry HTML refresh strategy. Bind application state schema to explicit release versions.
Worked scenario
When logic changes, publish app.abcd1234.js and let the new index reference that filename; do not silently replace a shared cached file.
What could go wrong
Aggressive service-worker caching can pin old HTML indefinitely.
Acceptance criteria
Test warm and cold clients and service-worker activation logic.
Source material and evidence boundaries
For the topic Prevent mixed HTML and JavaScript versions after a site update, use the sources listed below to check relevant methods. Any worked figures illustrate a scenario, not measured MojPlayWin performance. Consult the shared evidence standards before applying the method.