service-worker-network-caching-insufficient-for-push
A service worker configured only for network-first caching does not support push notifications. Push requires a push event handler in the service worker, VAPID key generation, and server-side Web Push subscription management. Many PWA scaffolds ship sw.js for offline caching only and omit all push infrastructure, creating a false sense of notification capability.
Related
- pwa-push-notifications-require-vapid-push-handler
- react-native-web-expo-is-antipattern-for-pwa
- docker
- ephemeral-tmp-pattern-for-zero-drift-github-sync
- openclaw
- service-worker-network-cache-is-not-push-notifications
- pwa-push-notifications-require-vapid-not-just-sw
- service-worker-caching-does-not-enable-web-push