Phase 3: PWA offline caching (frontend only)

Adds a real Workbox runtime-caching strategy on top of the Phase 1 app-shell
precache: StaleWhileRevalidate (cache-and-refresh) for the five read
endpoints (rooms/mine, open rooms, room messages, room members, invites/mine)
with a bounded/expiring cache per endpoint, while /api/auth/* and all
mutations stay network-only. An OfflineBanner (navigator.onLine-driven) and
a clearer Composer status line ("Connecting..." vs "You're offline") surface
what's actually happening; api/client.ts gains a NetworkError distinct from
ApiError so a genuine cache-miss-while-offline shows a quiet empty state
instead of a red error.

Manual offline testing (backend stopped, `vite preview` against the real
production service worker) surfaced a real gap the plan hadn't accounted
for: GET /api/auth/me is intentionally NetworkOnly, but that meant
ProtectedRoute could never confirm a session while offline and always
bounced to /login -- none of the newly-cached room/message data was ever
reachable. Fixed by caching a minimal, non-sensitive "last known user" in
localStorage (lib/lastUser.ts) and having AuthContext fall back to it for
any *unconfirmed* auth check (network failure, or a down backend answering
through a live reverse proxy with its own 502/503/504 -- both happen in
real deployments, not just literal airplane-mode). Only a server-confirmed
401 still clears it and signs the user out; every real action still
re-checks the actual session cookie server-side, so this can't grant
anything -- it only keeps cached UI reachable.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
2026-08-13 21:34:26 -06:00
co-authored by Claude Sonnet 5
parent e9fcb9fea2
commit aeb2f3f6a5
14 changed files with 333 additions and 53 deletions
+20 -5
View File
@@ -7,12 +7,27 @@ export class ApiError extends Error {
}
}
// Thrown when fetch() itself fails (e.g. offline with no cache entry for this
// request) -- distinct from ApiError, which means the server was reachable
// and responded with an error status. Callers use this to show a quiet
// "not available offline" state instead of a real-error message.
export class NetworkError extends Error {
constructor() {
super('Network unreachable')
}
}
export async function apiFetch<T>(path: string, init?: RequestInit): Promise<T> {
const response = await fetch(path, {
credentials: 'include',
headers: { 'Content-Type': 'application/json' },
...init,
})
let response: Response
try {
response = await fetch(path, {
credentials: 'include',
headers: { 'Content-Type': 'application/json' },
...init,
})
} catch {
throw new NetworkError()
}
if (!response.ok) {
let detail = response.statusText