pwa-push-notifications-require-vapid-push-handler
A service worker with only network-first caching does not enable push notifications. Real PWA push requires: a push event handler in sw.js, VAPID key pair generation, server-side Web Push Protocol subscription management, and browser permission grant. A sw.js file alone is not sufficient evidence that push notifications work.
Related
- docker
- r-same-m2-data-sources-m3-query-engine-foundation
- dual-claude-json-must-stay-identical-after-mcp-changes
- r-same-local-auth-v1-azure-ad-deferred
- 2026-04-04-oracle-001-self-architecture-analysis
- service-worker-network-caching-insufficient-for-push
- service-worker-network-cache-is-not-push-notifications
- pwa-push-notifications-require-vapid-not-just-sw
- service-worker-caching-does-not-enable-web-push