-
-
Notifications
You must be signed in to change notification settings - Fork 607
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lighthouse plugin make the process exit on latest build #4403
Comments
Hi @brendan-rice thank you for creating the issue! I've been out sick the last couple of days but will have a look tomorrow. I'm in the middle of preparing for the next major release of sitespeed.io so worst case it will not be fixed until then (probably next week). The disabled-by-default-lighthouse is a trace category for Chrome internal traces so it actually do not have anything to do with running Lighthouse or not (only what kind of trace events that will be in the trace). I will see happens when I run, in your case it looks like the Lighthouse plugin is running at all, not the GPSI plugin either (that also is enabled by default when you run that Docker container). |
Hi again, I see you are using version 36, that is not released yet, you can see latest releases on https://www.sitespeed.io/. Try with 35 and I hope that will work. Also I could see that there are flags you are using that do not exist for example --json-output true . Do you remember if that comes from AI? Best place for configuration is https://www.sitespeed.io/documentation/sitespeed.io/configuration/ or |
HI, i'm using the last version of sitespeed with lighthouse in docker and I have these messages : |
Hi @chosroes does it come from Lighthouse, can you share the full log please. Thanks! |
Have you read the documentation?
URL
https://www.bbc.co.uk
What are you trying to accomplish
I want to run lighthouse and have some of the key metrics around SEO, Accessibility and Performance output to json.
What browser did you use?
Chrome
How to reproduce
Log output
The text was updated successfully, but these errors were encountered: