Repository navigation
Tags
Tags
feat: timeoutMs, redirected-save check, removeMethod, classic service…
… worker build
- subscribe({ timeoutMs }) rejects with reason 'timeout' instead of hanging
on Chrome's quiet prompt or Brave
- a save answered by a redirect (lost session -> sign-in page) is save-failed
- unsubscribe({ removeMethod: 'POST' }) for POST /unsubscribe routes
- src/sw-classic.js (exports ./sw-classic): the SW handlers for plain-script
service workers via importScripts; generated from sw.js, test keeps it in sync
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
fix(client): name Chromium's AbortError (no push service, Brave, perm… …ission) (#1) subscribe() re-threw Chromium's raw 'Registration failed - push service error', which reads like the app failed. It means the browser has no reachable push service: ungoogled Chromium has none, Brave ships with it off. Map it to PushError 'no-push-service' / 'brave-push-off' (with the brave://settings fix), and Chromium's AbortError 'permission denied' to 'denied'. 0.1.3. Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
feat: @profullstack/notifications 0.1.0 Web Push with zero dependencies: VAPID + RFC 8291 from node:crypto, a browser client that fetches the key at runtime and names the reason push is unavailable, and service-worker handlers. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>