Files
web-at-transit/frontend
Bkk1234 0cf391afba PWA: publish an app version so stale shells are detectable
The service worker version had never moved past 1.0.0 and nothing on the page
said which build was loaded, so an old cached shell looked identical to a
fresh one.

- public/version.json: app, version, builtAt, pwa
- sw.js VERSION -> 2026.10.24.1 (new cache name, old caches dropped on activate)
- next.config: sw.js and version.json are served no-cache, no-store, plus
  Service-Worker-Allowed: / ; ui-manifest.json must-revalidate
- layout: <html data-app-version> read from version.json at build time
- PwaBoot: paints the version into the footer badge, polls /version.json
  (1.5s then every 5 min) and reloads once when it differs; guards against
  reload loops
- footer shows v2026.10.24.1 in mono next to the copyright

Verified: sw.js, /version.json and <html data-app-version> all report
2026.10.24.1, the footer badge shows it, and /stops renders the three search
tabs with the near-me panel in its own tab.
2026-10-24 00:27:23 +07:00
..
2026-05-24 22:55:17 +07:00
2026-05-24 22:55:17 +07:00
2026-05-24 22:55:17 +07:00
2026-05-24 22:55:17 +07:00
2026-05-24 22:55:17 +07:00
2026-05-24 22:55:17 +07:00
2026-05-24 22:55:17 +07:00

Frontend — Next.js App Router

npm install
npm run dev

Talks to backend purely via REST through nginx (/api/*, /files/*).