[vishnuv688]

What & why

DevTools.configure() accepted only eleven keys. port, hostname, captureScreenshots, filmstrip and emitArtifactsManifest are declared on DevToolsOptions, read by the plugin's constructor and documented in the README and on the website, but configure() dropped them. The plugin is constructed with no options, so configure() is the only way to set anything: those five always ran at their defaults, and a TypeScript caller got a type error while a JavaScript caller got silence.

This makes configure() take DevToolsOptions and apply all of them:

• Every option is applied. Option copying lives in helpers/configure-options.ts, keyed by a Record over DevToolsOptions, so an option added later fails to compile until it is handled instead of being silently dropped again.
• A rerun keeps its parent's backend. A rerun loads the test file again, so a configure({ port }) there would otherwise point the child at a port no dashboard is listening on. Port and hostname are skipped silently in that case, because that is the rerun working.
• Late port/hostname are refused with a warning. Once the backend start has begun they can no longer take effect, so the plugin logs a warning instead of doing nothing.
• Bad values are refused. null and an invalid port (NaN, out of range) are not applied.

Type of change

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Polish (an improvement to an existing feature)
• Breaking change (existing behavior changes for users)
• Documentation
• Internal (build, CI, dependencies, tooling)

Packages touched

• shared (types and contracts)
• core (framework-agnostic capture/reporting)
• elements (published element/snapshot API — @wdio/elements)
• service (WebdriverIO adapter)
• nightwatch-devtools (Nightwatch adapter)
• selenium-devtools (Selenium adapter)
• selenium-devtools-py (Selenium Python adapter)
• backend (server)
• app (UI)
• script (page-injected runtime)
• trace (Trace mode)

Notes for reviewers

• Why a helper. No test imports the plugin entry, because importing it patches selenium. The option-copying logic is extracted as a pure helper so it can be unit-tested. The lock decision (rerun vs. backend already starting) is a separate pure function with its own tests.
• Verification. pnpm build, pnpm test (2518 passed) and pnpm lint are green. Lint shows no new warnings: the same 4 as on main in this package.
• Not verified in a browser. This is option plumbing; no example run was done.
• Docs. The README already documented these options. It gains one note on when port/hostname take effect. The matching website page is updated in the companion webdriverio docs PR, which should merge after this ships in a release.

🤖 Generated with Claude Code

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge, with one non-blocking correction to the release note.

Findings

1.  Missing promised warning ▶

Summary

DevTools.configure() now applies the previously ignored server and capture options.

• Selenium DevTools applies the options passed to configure().
• Backend address settings stay with the backend that starts or is reused.

_{Reviews (2) · Last reviewed commit: "fix(selenium-devtools): refuse configure..." · Reviewed by Greptile}