Lighthouse-ci: How to run for both desktop and mobile?

[felixck12]

Hello. We are using lhci autorun in our github actions and we'd like to analyze some pages for both mobile and desktop using the emulatedFormFactor setting. We will be uploading the results to our own lhci server.

Our ideal end result would be to have a report rendered that displays both results for mobile and desktop the same way PageSpeed Insights give you a toggle between the mobile and desktop.

Curious if there is a way to do this without needed to
A) Run two separate autorun commands with a config for mobile and one for desktop
B) If we can avoid having to setup two separate projects for desktop and mobile on our server to avoid commit hash conflicts.

Thanks in advance!

[patrickhulce]

hey @felixck12 thanks for filing! Smoother mobile and desktop simultaneous support is on our radar since right now it's a bit complicated to get them to live together.

To get it working today:

• You can't use lhci autorun, must use collect/assert/upload separately.
• You'll need to invoke collect twice with the --additive flag, ensuring the mobile and desktop URLs are different
  lhci collect --additive --settings.configPath=./path/to/desktop-config.js --url=http://localhost/?desktop
lhci collect --additive --settings.configPath=./path/to/mobile-config.js --url=http://localhost/?mobile
• Run the rest of the steps as usual lhci assert; lhci upload

So to answer your questions directly...

Run two separate autorun commands with a config for mobile and one for desktop

Not a way around this, you'll have to collect two separate times with different settings.

If we can avoid having to setup two separate projects for desktop and mobile on our server to avoid commit hash conflicts.

Yes, if you use collect --additive and the URLs are different they can live in the same project and builds.

[felixck12]

Thanks @patrickhulce I will give this a try.

[kmcrawford]

Is this still on the radar? I see this issue is 6 months and still very much needed!

[patrickhulce]

Yes still on the radar @kmcrawford. This issue wouldn't unlock any new functionality you can't accomplish today though so it's definitely not high on the list. If you'd like it to be prioritized then +1 the issue itself (the first original comment).

I'd also suggest a recalibration of your expectations for how quickly single person open source projects can finish their entire backlog or you'll have many more disappointments to come, Lighthouse CI or otherwise ;)