Skip to content

chore: upgrade playwright to 1.62.1 - #1

Closed
marcomaes wants to merge 1 commit into
mainfrom
chore/upgrade-playwright-1.62.1
Closed

chore: upgrade playwright to 1.62.1#1
marcomaes wants to merge 1 commit into
mainfrom
chore/upgrade-playwright-1.62.1

Conversation

@marcomaes

Copy link
Copy Markdown
Owner

Summary

  • Bumps playwright-core/playwright/@playwright/test to 1.62.1 across all workspaces.
  • playwright-core ≥1.60.0 dropped the separate internal files this repo required directly (lib/generated/injectedScriptSource.js, lib/utils/isomorphic/locatorUtils.js) in favor of one opaque lib/coreBundle.js. Adds a postinstall script (scripts/sync-playwright-injected-script.mjs) that auto-extracts the injected-script engine source from whatever playwright-core version is installed, and hand-vendors the small, stable selector-string builders in packages/mobilewright-core/src/selector-builders.ts — so future Playwright bumps stay low-effort instead of requiring a rewrite.
  • Playwright's expect() web-first matchers now gate on receiver._apiName === 'Locator' instead of receiver.constructor.name; MobileWebViewLocator now sets _apiName so expect(locator).toBeVisible() etc. keep working.

Test plan

  • npm run build
  • npm run lint
  • npm run test (597 passed, 1 skipped)
  • Deleted packages/mobilewright-core/src/generated/ and re-ran npm install to confirm postinstall regenerates it from a clean state

🤖 Generated with Claude Code

@marcomaes

Copy link
Copy Markdown
Owner Author

Superseded by mobile-next#274 (PR against upstream).

@marcomaes marcomaes closed this Aug 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant