Repository navigation
v0.16.0
Three browser stores
Playwright, Cypress, and Puppeteer download a browser or a binary bundle and
keep it in one folder. Exodrive moves that folder and puts a symbolic link in
its place, so each tool keeps reading the path it knows.
| Provider | What moves | Variable |
|---|---|---|
playwright |
The browsers that Playwright downloaded | PLAYWRIGHT_BROWSERS_PATH |
cypress |
The binary bundle that Cypress downloaded | CYPRESS_CACHE_FOLDER |
puppeteer |
The browsers that Puppeteer downloaded | PUPPETEER_CACHE_DIR |
PLAYWRIGHT_BROWSERS_PATH=0 tells Playwright to keep the browsers in
node_modules. The provider reads the system cache folder for that value, so
the string 0 never becomes a path.
No process lock names these tools. The run that reads the store is node, and
the browser program names are shared with programs that never touch the folder.
A name lock would miss the writer or stop an unrelated program, so the row
carries the next step instead.
Evidence on a real store
This Mac holds 1.19 GB of Playwright browsers (9 folders, 787 files).
$ exodrive check
Playwright Brow.. package_store 1.1 GB Migrated symlink ...gley/Library/Caches/ms-playwright
$ time exodrive migrate --target=/Volumes/PHD/… --tools=playwright
✅ Migrated Playwright Browsers.
Migration completed. Reclaimed 1.1 GB on the local disk.
16.315 total
$ exodrive verify --all
[ok] playwright.browsers: …/playwright/browsers (787 files, 1.1 GB)
$ ls -ld ~/Library/Caches/ms-playwright
lrwxr-xr-x … ms-playwright -> /Volumes/PHD/…/playwright/browsers
The browser runs from the linked folder:
$ ~/Library/Caches/ms-playwright/chromium_headless_shell-1254/…/chrome-headless-shell --version
Google Chrome for Testing 158.0.8127.18
exodrive rollback playwright.browsers restored a real folder with the same
1.1 GB, and the ledger was empty again. The move used a separate record file,
so the record of this Mac stayed untouched.
What this release does not prove
A full Playwright test run through the link was not run: this Mac has the
browsers, not a project that starts them. The browser binary itself runs from
the linked folder, which covers the read path.