[Vidal Ortega (vidorteg)]

Launching a new Edge instance sometimes failed to auto-attach DevTools, because Edge can hand off to another process and exit before its debugging port is ready.

Instead of relying on puppeteer.launch, the extension now starts Edge itself and keeps retrying the connection to the debugging port until a page is available or the configured timeout expires.

The launch only fails early if Edge exits with an error code, and the existing timeout setting is now respected for all launch paths.

[Copilot]

🟡 Changes recommended

Connection attempts can exceed the launch deadline without being interrupted by process failures, and failed launches can leave owned Edge processes running.

2 open issues

• Terminate the spawned browser when launch fails · New
• Bound CDP connection attempts by the launch deadline · New

What changed in this PR

This PR addresses intermittent DevTools auto-attach failures when Edge hands off startup to another process and exits before its debugging port is ready.

Changes:

• Replaces puppeteer.launch with direct process spawning, connection retries, and page-readiness checks.
• Passes the configured timeout through normal and remote launch paths.
• Updates mocks and adds launcher tests for handoffs, startup failures, timeouts, and disconnection.

File	Description
test/​utils.test.ts	Verifies launcher delegation, arguments, and default timeout.
test/​puppeteerCoreStub.ts	Replaces the launch mock with argument and connection mocks.
test/​extension.test.ts	Updates launch expectations to include the timeout.
test/​browserLauncher.test.ts	Adds coverage for connection retries and launch outcomes.
src/​utils.ts	Delegates browser startup to the new helper with a timeout.
src/​extension.ts	Forwards configured timeouts across browser launch paths.
src/​browserLauncher.ts	Implements Edge spawning, connection retries, and page-readiness checks.

_{Review effort: Balanced}

[Guangyue Xu (guangyuexu)]

LGTM