[gimler]

Allow launch() to connect to a remote Playwright browser through wsEndpoint, configured directly, through the builder or from environment variables.

Document the separate-container setup, add a changelog entry and preserve positional logger compatibility.

Related to playwright-php/playwright-symfony#57.

[gimler]

depends on #186

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[gimler]

@kbond can you take a look please

[kbond]

Yep, just went through the bugs to create a bug fix release. Going to go through the features soon.

[kbond]

@gimler I added some tests and docs, can you take a look?

[smnandre]

With wsEndpoint set, launch() connects instead of launching, so launch-only options (headless, args, channel, executable path) are ignored without notice. A log warning or a documentation note would make that explicit.

connect() now always sends the configured context options, including on explicit connect() calls. Existing connect() callers get a context configured differently from before, which belongs in the changelog.

[kbond]

Good catch. I clarified in the guide that browser launch options belong on the remote server. Configured context settings now apply only when launch() uses wsEndpoint. An explicit connect() still creates its initial context with Playwright defaults.

[smnandre]

Thank you @gimler and @kbond