You might not need a service worker
6 hours ago
- #caching
- #web-development
- #service-workers
- Service workers, once a 'next big thing', are now largely forgotten due to complexities and risks, such as bad cache strategies causing stale app issues.
- Neciu's post explores use cases for service workers, including Slack's instant boot via caching assets and state, but suggests HTTP caching might suffice for many apps.
- Other examples like keeping dead chunks alive across deploys, Mux's manifest rewriting, Partytown, and Mock Service Worker often have alternative solutions or server-side options.
- Service workers are essential only for specific features like offline support, push notifications, and background sync; outside these, simpler alternatives often exist.
- The author questions the necessity of service workers for most problems and invites examples to revisit their use.