v0.1.4

• subscribe({ timeoutMs }): gives up with reason timeout instead of hanging on Chrome's quiet prompt or Brave.
• A save answered by a redirect (lost session sent to sign-in) now throws save-failed.
• unsubscribe({ removeMethod: 'POST' }) for POST /unsubscribe routes (default DELETE).
• @profullstack/notifications/sw-classic: service-worker handlers for plain-script workers via importScripts.

v0.1.3

subscribe() now names Chromium's AbortError instead of echoing "Registration failed - push service error": PushError reason 'no-push-service' (ungoogled Chromium and other builds without a push service) or 'brave-push-off' (with the brave://settings/privacy fix), and Chromium's AbortError permission-denied maps to 'denied'. (#1)

v0.1.2

vapidKeysFromEnv also reads VAPID_PUBLIC / VAPID_PRIVATE. The ttl option is documented: 24h default, where web-push used 4 weeks.

v0.1.1

sendPush errors now include the push service's response text (trimmed to 300 chars), e.g. push service answered 403: invalid JWT provided.

v0.1.0

First release: zero-dependency Web Push server (VAPID + RFC 8291), runtime-key browser client that names why push is unavailable, service-worker handlers.