[web] Deprecate and remove `flutter_service_worker.js`
### Document Link https://flutter.dev/go/web-cleanup-service-worker ### What problem are you solving? The current default service worker implementation is one of (several) approaches that can be used by Flutter web, however it's not a good fit for all use-cases. This confuses users when it doesn't behave as they expect. Having a default service worker implementation sends the message that it is *necessary* or *recommended* by Flutter web to function correctly, but that is not the case. This design doc discusses how the current implementation of `flutter_service_worker.js` is going to be phased out (TL;DR: with a cleanup service worker for those currently using the default one), and how the flutter tools and flutter.js will eventually stop generating (or loading) a default service worker, allowing web app developers to do what's best for their specific apps.
Posted by ditman on Oct 15, 2024, 8:05 PM
Tags
Related issues
- 2026 - Microsoft Office 365
- [Ubuntu] `ubuntu-latest` label will use Ubuntu 26.04 in November 2026
- Gamut mapping
- [Codex Desktop] Editing and resending a queued message triggers "App-server queued follow-up no longer exists"
- [Windows] ChatGPT 26.820.60940 fails with "invalid transport in mcp_servers.codex_app"; Beta 26.727.40816 works
- [BUG]: infinite loading of videos
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
github (SaaS)
2026 - Microsoft Office 365
[Ubuntu] `ubuntu-latest` label will use Ubuntu 26.04 in November 2026
Gamut mapping
[Codex Desktop] Editing and resending a queued message triggers "App-server queued follow-up no longer exists"
[Windows] ChatGPT 26.820.60940 fails with "invalid transport in mcp_servers.codex_app"; Beta 26.727.40816 works
[BUG]: infinite loading of videos
Restore GPT-5.6 Sol’s 372k Codex context window, or provide an opt-in setting
Codex Desktop for macOS repeatedly triggers `syspolicyd` / `trustd` CPU and memory runaway
[web] Deprecate and remove `flutter_service_worker.js`
### Document Link https://flutter.dev/go/web-cleanup-service-worker ### What problem are you solving? The current default service worker implementation is one of (several) approaches that can be used by Flutter web, however it's not a good fit for all use-cases. This confuses users when it doesn't behave as they expect. Having a default service worker implementation sends the message that it is *necessary* or *recommended* by Flutter web to function correctly, but that is not the case. This design doc discusses how the current implementation of `flutter_service_worker.js` is going to be phased out (TL;DR: with a cleanup service worker for those currently using the default one), and how the flutter tools and flutter.js will eventually stop generating (or loading) a default service worker, allowing web app developers to do what's best for their specific apps.
Comments (0)
No comments yet. Start the discussion.