Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

CLI tries to launch a Chrome instance even when given a remote hostname

See original GitHub issue

Provide the steps to reproduce

Run LH on any URL via the CLI, passing --hostname and --port to point at a remote Chrome instance

What is the current behavior?

Lighthouse launches a local Chrome instance, but ignores it and connects to the remote instance anyways. If this isn’t possible because Chrome isn’t installed (for example, in CI environments), the entire Lighthouse run crashes out.

What is the expected behavior?

Lighthouse doesn’t launch a local Chrome instance (and fail the run if it isn’t installed); it just connects to the remote instance.

Environment Information

Affected Channels: CLI
Lighthouse version: 7.2.0
Chrome version: N/A
Node.js version: 14.15.4
Operating System: macOS Catalina 10.15.7

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:9 (3 by maintainers)

Top GitHub Comments

1reaction

connorjclarkcommented, Feb 25, 2021

Thanks for taking this, Tyler! let us know if you have any questions.

1reaction

patrickhulcecommented, Feb 25, 2021

Thanks for filing @tkindy!

No this issue is really somewhat unrelated to chrome-launcher, if a hostname other than localhost is used, then lighthouse shouldn’t even be trying to launch Chrome.

AFAICT, lighthouse should still respect the hostname setting but you’ll have a useless Chrome launched and sitting around on your localhost as well (and this might fail if Chrome can’t be started on your machine).

https://github.com/GoogleChrome/lighthouse/blob/fb18dfe70e89d752a46deabe2de8a21b414ceb7e/lighthouse-core/index.js#L38-L45

Either way we’ll want to fix that up on the lighthouse side.