Case Study - A free Chrome extension for stubborn localhost state

Overview

Service Worker Manager started as an internal fix for a recurring local-development problem. While working on a client project with a service-worker-heavy frontend, we kept switching between apps that reused the same localhost origins and ports. Old service workers and Cache Storage entries survived the switch, served stale assets, and made healthy codebases look broken.

We built a small internal tool to make that state visible and removable without dropping into DevTools every time. Once it proved useful across our own workflow, we published it as a free-to-use, Chrome extension for developers who need a faster way to inspect the current origin, clear stale state, and move on with their day.

What we did

We turned that internal utility into a focused product with one clear job: show developers what is still attached to the current origin and give them a reliable reset path. Service Worker Manager surfaces active service workers and named caches, then lets the user unregister, clear, or reset both in one pass. For stubborn cases where a page is still controlled by stale state, there is an optional reload step immediately after cleanup.

The scope is intentionally narrow. The extension acts on the current active tab origin, keeps permissions tight, and processes everything locally in the browser. That gives developers a tool that feels predictable: no broad cleanup, no remote services, no telemetry, and no mystery about what will be touched.

We also positioned it the way we wish more developer utilities were positioned: free to use, immediately practical, and honest about who it is for. This is not a general browser cleaning tool. It is aimed at developers working with PWAs, offline-first apps, or local environments where service workers and caches can linger longer than they should.