scope: remove PWA and service-worker surface #142

New issue

Closed

opened 2026-03-28 18:57:59 +00:00 by barrettruth · 0 comments

barrettruth commented

2026-03-28 18:57:59 +00:00

Decision

Remove the PWA/service-worker surface for now.

Installability and offline caching are not part of the current scope. The existing Serwist/service-worker setup adds deployment and stale-cache risk without supporting the core single-user tracker launch.

Solution

Remove Serwist wrapping from Next config.
Remove src/sw.ts and generated service-worker assumptions.
Remove PWA-only manifest/installability metadata if it is not useful without PWA support.
Drop @serwist/next and serwist dependencies.
Clean any seed/demo references that imply PWA work remains active.

Acceptance criteria

next build and just ci pass without Serwist.
The app no longer registers or serves a service worker.
No open tracker item presents PWA/offline installability as a launch requirement.

## Decision Remove the PWA/service-worker surface for now. Installability and offline caching are not part of the current scope. The existing Serwist/service-worker setup adds deployment and stale-cache risk without supporting the core single-user tracker launch. ## Solution - Remove Serwist wrapping from Next config. - Remove `src/sw.ts` and generated service-worker assumptions. - Remove PWA-only manifest/installability metadata if it is not useful without PWA support. - Drop `@serwist/next` and `serwist` dependencies. - Clean any seed/demo references that imply PWA work remains active. ## Acceptance criteria - `next build` and `just ci` pass without Serwist. - The app no longer registers or serves a service worker. - No open tracker item presents PWA/offline installability as a launch requirement.