Location:.gitea/workflows/ci.yml — nothing runs after "Build" except size reporting
Problem
npm run build succeeding proves the bundler finished, not that the app boots. A wrong asset base path, a broken config.json copy, a service-worker registration error, or a top-level module throwing on load all produce a blank page that would deploy to chat.lotusguild.org unnoticed for ~11 minutes plus however long it takes someone to notice. The README itself warns that a blank page is "almost always a failed module/asset resolution".
Suggested fix
After the build, start npx vite preview --port 4173 &, wait for it, then run a headless Chromium (or even curl + a tiny Playwright script) that loads /, waits for the root element to have children, and fails on any pageerror or console error. This can share the Playwright setup from the smoke-test issue, but is worth doing even standalone since it needs no homeserver.
Filed from the September 2026 client audit (CI pipeline review, branch lotus @ 4bea4895).
**Location:** `.gitea/workflows/ci.yml` — nothing runs after "Build" except size reporting
### Problem
`npm run build` succeeding proves the bundler finished, not that the app boots. A wrong asset base path, a broken `config.json` copy, a service-worker registration error, or a top-level module throwing on load all produce a blank page that would deploy to chat.lotusguild.org unnoticed for ~11 minutes plus however long it takes someone to notice. The README itself warns that a blank page is "almost always a failed module/asset resolution".
### Suggested fix
After the build, start `npx vite preview --port 4173 &`, wait for it, then run a headless Chromium (or even `curl` + a tiny Playwright script) that loads `/`, waits for the root element to have children, and fails on any `pageerror` or console error. This can share the Playwright setup from the smoke-test issue, but is worth doing even standalone since it needs no homeserver.
---
_Filed from the September 2026 client audit (CI pipeline review, branch `lotus` @ 4bea4895)._
jared
added this to the Audit 2026-09 · Medium & Low milestone 2026-09-12 01:57:43 -04:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Location:
.gitea/workflows/ci.yml— nothing runs after "Build" except size reportingProblem
npm run buildsucceeding proves the bundler finished, not that the app boots. A wrong asset base path, a brokenconfig.jsoncopy, a service-worker registration error, or a top-level module throwing on load all produce a blank page that would deploy to chat.lotusguild.org unnoticed for ~11 minutes plus however long it takes someone to notice. The README itself warns that a blank page is "almost always a failed module/asset resolution".Suggested fix
After the build, start
npx vite preview --port 4173 &, wait for it, then run a headless Chromium (or evencurl+ a tiny Playwright script) that loads/, waits for the root element to have children, and fails on anypageerroror console error. This can share the Playwright setup from the smoke-test issue, but is worth doing even standalone since it needs no homeserver.Filed from the September 2026 client audit (CI pipeline review, branch
lotus@4bea4895).