How to roll Playwright dependency
Steps
Obtain latest Playwright version
npm info playwright@next versionUpdate Playwright packages in
package.json:- Update
playwrightandplaywright-core(dependencies) and@playwright/test(devDependency) to the target version. - Run
npm installto updatepackage-lock.json. - Verify with
npm ls playwright-corethat the rootplaywright-coreactually rolled — it is pinned directly inpackage.jsonand is whatplaywright-cli.jsruns; forgetting it leaves the CLI on the old version while tests pass against the new@playwright/test.
- Update
Run the update script to sync skills and README:
node scripts/update.jsThis script:
- Runs
node playwright-cli.js install --skillsto regenerate skills from the new Playwright version. - Copies the generated skills from
.claude/skills/playwright-cli/intoskills/playwright-cli/. - Cleans up the generated
.claude/skills/directory.
- Runs
Update README.md with relevant changes from the updated skill at
skills/playwright-cli/SKILL.md. Compare the skill file with the README and update any sections that are out of date (commands, flags, default behaviors, examples).Verify the CLI works:
node playwright-cli.js --helpTest the CLI:
npm run testCreate a branch and commit:
- Branch name:
roll_<version>(e.g.roll_214) - Commit message:
chore: roll Playwright to <version> - do not add Co-Authored-By
- Branch name:
Key files
| File | Role |
|---|---|
package.json |
Playwright version pins (playwright, @playwright/test) |
playwright-cli.js |
CLI entry point — requires Playwright's program module |
scripts/update.js |
Automation script for syncing skills and README after version bump |
skills/playwright-cli/SKILL.md |
Skill definition installed from Playwright (source of truth for commands) |
README.md |
User-facing docs — must reflect current skill commands and behavior |