Emergency revert to monolith + SW killer (site is down)#31
Merged
Conversation
The Tailwind precompile + JS extraction (PR #28) introduced a script-order bug and a service worker that cached the broken HTML. PRs #29-#30 tried to fix it but the CDN lag + stuck SW cache made the site unrecoverable without manual DevTools intervention. This commit restores the working v2.6.0 monolithic index.html (205KB, inline JS, Tailwind CDN) and adds an aggressive inline SW-killer script that: - Unregisters all service workers - Deletes all caches - Runs immediately on page load (even from cached HTML) Split artifacts removed: app.js, styles.css, src/inline.css, tailwind.config.js, package.json, package-lock.json. Kept from the v3 era: og-preview.png, manifest.json, ROADMAP.md, .github/workflows/validate.yml (updated for monolith), sw.js (self-destruct stub). The monolith split is a good idea but needs to be done without a service worker in the same PR. Deferred to a future pass.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Emergency revert — site is down
The v3.0.0 Tailwind/monolith split (PR #28) broke the site. PRs #29-#30 couldn't fix it because the service worker cached the broken HTML and the CDN lagged behind the fixes.
What this does
index.html(205KB, inline JS, Tailwind CDN) — the last version that worked<body>that unregisters all service workers and deletes all caches on page load. This runs even from cached HTML because'unsafe-inline'is in the CSP.app.js,styles.css,src/inline.css,tailwind.config.js,package.json,package-lock.jsonog-preview.png,manifest.json,ROADMAP.md,.github/workflows/validate.yml(updated for monolith),sw.js(self-destruct stub)Why
The monolith split needs to be done without a service worker in the same PR. Shipping both at once created an unrecoverable state: broken HTML cached by SW → user sees broken page → can't get fix because SW serves cached content → fix can't propagate.
Test plan
Generated by Claude Code