mirror of
https://github.com/home-assistant/frontend.git
synced 2026-08-17 02:23:22 +01:00
* Recover from a stale index.html at boot A cached, stale index.html imports the previous build's content-hashed entry bundles (core.<hash>.js / app.<hash>.js). After an upgrade those files 404, app.js never runs, <home-assistant> is never defined, and the launch screen never clears. No bundled JS can recover this, because the bundle itself failed to load. Add a tiny, prod-only inline guard in index.html that catches the failed entry load (capture-phase resource error + unhandledrejection) and does a single, loop-guarded cache-busting reload, dropping the service worker and caches on https first. core.ts strips the cache-bust param after a successful boot. Part of home-assistant/epics#113. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * Share stale-build recovery patterns via a single JSON source Move the boot guard's chunk-detection regexes into stale-build-patterns.json and inject them into the inline guard at build time (entry-html.js), so they stay in sync with the bundled recovery util (util/recover-stale-build.ts, in the follow-up post-boot recovery) which reads the same file — no more manually kept-in-sync copies. Part of home-assistant/epics#113. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>