Media
3 items
Description
Is this tab on the old version after a deploy, and why? Checks its build, its HTML, its service worker and its files. You deployed, but a tab still shows the old version. Click the button on that tab to find out why. stale-deploy-check looks at the tab from inside the browser: • Its build: it compares the tab's build id (or, without one, the files it loaded) with what the server sends now. • Where its HTML came from: the network, the browser cache, a 304, or a service worker. • The service worker: whether one controls the tab, whether a new one is waiting to take over, and whether its cache holds an old copy of the page. • The files the tab loaded: whether the deploy deleted them, which leaves an open tab one click away from a blank screen. When it finds a problem, it says which layer kept the old version, shows the evidence, and suggests the fix, with a link to the article section that explains it. "Copy prompt to fix" copies a prompt for your coding agent with everything it needs to fix it in your repo. It only runs when you click it, and only on that tab. It reads the tab, requests that page and its files from the site, and shows the result. Nothing is sent anywhere else, and nothing is stored. Built on the article "We Deployed an Hour Ago. Why Do Users Still See the Old Version?": https://ihabkhattab.com/blog/deployed-but-users-see-the-old-version/ The same checks run from the command line and in CI: https://github.com/ikhattab/stale-deploy-check
rating_count is the Chrome Web Store ratings count, not a written-review count.