Summary
Deploy scripts bump CONFIG.APP.VERSION, but that value currently only updates the visible header label. It does not reliably force browsers to load new JS/CSS after deploy.
Affects:
Deploy scripts:
update-token-client.sh
update-tokentest.sh
Problem
index.html loads assets with static URLs, e.g.:
./css/base.css
./js/app.js
No query-string versioning or reload check exists (unlike /farm, which uses version.html + version-check.js).
After deploy, users may continue running cached JS/CSS until a hard refresh.
Possible approaches
Option A — Query-string cache busting
Append version to asset URLs in index.html, e.g. ./js/app.js?v=0.0.11
- Could be applied during deploy script rewrite
- Or injected from
config.js for module entry only (limited coverage)
Option B — Farm-style version check
Add version.txt / version.html + small reload-on-change script
- Proven pattern elsewhere in this repo
Option C — Both
- Version file for reload detection
- Query strings for individual assets
Acceptance criteria
Priority
Medium
Summary
Deploy scripts bump
CONFIG.APP.VERSION, but that value currently only updates the visible header label. It does not reliably force browsers to load new JS/CSS after deploy.Affects:
/token/tokentestDeploy scripts:
update-token-client.shupdate-tokentest.shProblem
index.htmlloads assets with static URLs, e.g.:./css/base.css./js/app.jsNo query-string versioning or reload check exists (unlike
/farm, which usesversion.html+version-check.js).After deploy, users may continue running cached JS/CSS until a hard refresh.
Possible approaches
Option A — Query-string cache busting
Append version to asset URLs in
index.html, e.g../js/app.js?v=0.0.11config.jsfor module entry only (limited coverage)Option B — Farm-style version check
Add
version.txt/version.html+ small reload-on-change scriptOption C — Both
Acceptance criteria
/tokenand/tokentestPriority
Medium