The SW cache key (bitvid-sw-YYYY-MM-DD) and the informational meta in
index.html/embed.html were hand-bumped, so client caches only invalidated when
someone remembered to change the date — stale app shells (and stale footer
versions) persisted across deploys.
build-dist now stamps the dist artifacts with `bitvid-sw-<buildDate>-<hash8>`
(same content hash shown in the footer), so every content change yields a new
cache name and the SW's activate step drops the old cache automatically. Only
the dist output is rewritten — the committed (minified) sw.min.js source is left
as-is, so the sw-compat guard and tests that reference the source value are
unaffected. Build verified: all three dist files share one stamped version,
dist/sw.min.js still parses, verify:dist:deploy-artifact passes.
Also confirmed `npm run build` is reproducible (same inputs => same hash), so
deploys are deterministic.
Co-Authored-By: Claude Opus 4.8 <[email protected]>
- Moved `<!-- VERSION_INFO -->` out of `.fade-in` container in `index.html` to prevent visibility issues if JS fails.
- Added verification in `scripts/build-dist.mjs` to ensure `dist/components` exists and is not empty.
- Added logging to `scripts/build-dist.mjs` for version injection status.
- Updated `scripts/verify-dist-deploy-artifact.mjs` regex to accommodate HTML structure change.
Co-authored-by: PR0M3TH3AN <[email protected]>
- Relaxed `engines.node` in `package.json` from `>=22` to `>=20` to match the hosting environment (Node 20.x), resolving strict engine failures during install.
- Modified `scripts/build-dist.mjs` to throw an error (instead of warning) if version injection fails, preventing silent failures.
- Updated `npm run build` to include `verify:dist:deploy-artifact` as a mandatory post-build step, ensuring the final artifact contains the expected version markup.
Co-authored-by: PR0M3TH3AN <[email protected]>
Previously, `scripts/build-dist.mjs` caught errors during version injection and logged them but allowed the build to complete with a success exit code. This masked issues in CI/CD environments (like 4everland) where version injection failed silently, leading to deployments without version hashes.
This change modifies `injectVersionInfo` to `process.exit(1)` upon failure, ensuring that any issue with version injection halts the build pipeline and surfaces the error in the logs.
Tested locally by simulating injection failure (verified exit code 1) and by running a standard build (verified success and correct injection).
Co-authored-by: PR0M3TH3AN <[email protected]>
Replaced the fragile regex-based version injection in `scripts/build-dist.mjs` with a robust placeholder method.
- Added `<!-- VERSION_INFO -->` placeholder to `index.html`.
- Updated `scripts/build-dist.mjs` to target the placeholder, while retaining regex fallback for safety.
- Ensures version info is reliably injected during local builds regardless of code formatting.
Co-authored-by: PR0M3TH3AN <[email protected]>
Refactored scripts/hash-dist.mjs to export buildHashState and support module import.
Modified scripts/build-dist.mjs to calculate the dist hash after asset rewriting and inject it along with the current date into dist/index.html below the tagline.
Verified with Playwright screenshot.
Co-authored-by: PR0M3TH3AN <[email protected]>
