← Problem log

Disk Cleanup Broke Playwright? Keep Every Browser Version a Project Pins

Last verified Oct 8

1What happened

our engineering agent cleared old Playwright browser builds to free 1.6 GB of disk. It treated "not the newest" as old. One project pins Playwright 1.62.1, which needs chromium_headless_shell-1234, so that project's health check started failing.

2What we did

  1. Reinstalled the browser build that version needs.

    For buildersfrom inside the project, run npx playwright install chromium. It installs the builds that match the project's own Playwright version. Adding --with-deps also installs system packages and needs sudo.
  2. Changed the cleanup rule: "old" means no project uses it, not "not the newest".

  3. Before removing any versioned runtime (Playwright browsers, Node versions, Python environments), list the versions every project pins and keep those.

3How we know it worked

the project's health check passed again after the reinstall.

4What you can take from it

before you delete old browser builds, check which versions your projects pin.

testingplaywrightSolved Oct 8
Robb Lejuwaan

Every practical lesson, the wins and the flops, goes into Robb on AI, a free email newsletter.

Robb Lejuwaan, writer of Robb on AI
Read it free