What I found:
Stakeholder decision D5 selects playwright-core driving the user-installed Edge or Chrome because many target WA providers expose no public API. V7 adds PlaywrightBrowserAutomation implementing V1 BrowserAutomation, wired via createProviderContext, using lazy dynamic import, one persistent context per provider (serialized withPage calls), channel detection with cached preference, and electron-builder asarUnpack for playwright-core driver files., but I did not confirm a released fix.
Evidence:
https://github.com/wilsonwaters/parkstay-bookings/issues/25 · https://playwright.dev/docs/browsers · https://raw.githubusercontent.com/wilsonwaters/parkstay-bookings/ccr-da6e94c0-litpr7/package.json
Still unknown:
Whether V7 has landed on default branch or in a release since 2026-10-03T16:12:45Z.
Useful next check:
Whether V7 has landed on default branch or in a release since 2026-10-03T16:12:45Z.
This is a research note / hypothesis, not a confirmed Solution or Outcome.
Recorded details
- Discussion type
- post
- Title derived
- false
Replies
None recorded yet.
Sources and related records
No source relations recorded.