LanternError: Invalid dependency graph created, cycle detected

[markbmullins]

FAQ

• Yes, my issue is not about variability or throttling.
• Yes, my issue is not about a specific accessibility audit (file with axe-core instead).
• Yes, my issue is not answered by other FAQs.

URL

https://www.churchandunioncharleston.com/

What happened?

LanternError: Invalid dependency graph created, cycle detected

const command = `npx lighthouse '${business.url}' --chrome-flags="--headless=new --disable-gpu --no-sandbox" --output=json,html --output-path=${businessTempDir}/${reportBaseName} --only-categories=performance,seo,accessibility,best-practices --form-factor=mobile --throttling.rttMs=150 --throttling.throughputKbps=1638 --throttling.cpuSlowdownMultiplier=4  --save-assets --quiet`;

Trace logs:

report-business-105-1741555332181-0.devtoolslog.json
report-business-105-1741555332181-0.trace.json

What did you expect?

The lighthouse script to report the website without error.

What have you tried?

I've tried playing around with different args like removing the throttling, but get the same result.

How were you running Lighthouse?

CLI

Lighthouse Version

12.4.0

Chrome Version

No response

Node Version

v22.10.0

OS

Mac os

Relevant log output

[markbmullins]

It appears to be the performance category causing the issue.

This errors:

npx lighthouse 'https://www.churchandunioncharleston.com/' --chrome-flags="--headless=new --disable-gpu --no-sandbox" --output=json,html --output-path=./lighthouse-report --only-categories=performance,seo,accessibility,best-practices --form-factor=mobile --throttling.rttMs=150 --throttling.throughputKbps=1638 --throttling.cpuSlowdownMultiplier=4 --save-assets --quiet

This does not:

npx lighthouse 'https://www.churchandunioncharleston.com/' --chrome-flags="--headless=new --disable-gpu --no-sandbox" --output=json,html --output-path=./lighthouse-report --only-categories=seo,accessibility,best-practices --save-assets --quiet

and this does not:

npx lighthouse 'https://www.churchandunioncharleston.com/' --chrome-flags="--headless=new --disable-gpu --no-sandbox" --output=json,html --output-path=./lighthouse-report --only-categories=seo,accessibility,best-practices --form-factor=mobile --throttling.rttMs=150 --throttling.throughputKbps=1638 --throttling.cpuSlowdownMultiplier=4 --save-assets --quiet

[adamraine]

Yeah this is pretty easy to reproduce. Seems to happen in the trace engine.

I uploaded the performance trace to https://trace.cafe/t/eJP0YJ9SBw, and opening the console on that page shows a similar error.