hostname The hostname to use for the debugging protocol. port The port to use for the debugging protocol. If omitted, any detected Chrome Canary or Chrome stable will be used. For a full list of flags, see Īdditionally, use the CHROME_PATH environment variable to use a specific Chrome binary. chrome-flags Custom flags to pass to Chrome (space-delimited). WARNING: If the -config-path flag is provided, this preset will be ignored. config-path The path to the config JSON.Īn example config file: core/config/lr-desktop-config.js additional-trace-categories Additional categories to capture with the trace (comma-delimited). list-trace-categories Prints a list of all required trace categories and exits list-all-audits Prints a list of all available audits and exits save-assets Save the trace contents & devtools logs to disk quiet Displays no progress, debug logs, or errors Lighthouse requires Node 18 LTS (18.x) or later. Users who want more advanced usage, or want to run Lighthouse in an automated fashion should use the Node CLI.
The Node CLI provides the most flexibility in how Lighthouse runs can be configured and reported. Run it: follow the extension quick-start guide.
Installation: install the extension from the Chrome Web Store. The Chrome extension was available prior to Lighthouse being available in Chrome Developer Tools, and offers similar functionality. Run it: open Chrome DevTools, select the Lighthouse panel, and hit "Generate report".
Lighthouse is integrated directly into the Chrome DevTools, under the "Lighthouse" panel. How do I author custom audits to extend Lighthouse?.How do I get localized Lighthouse results?.How does Lighthouse use network throttling, and how can I make it better?.
0 kommentar(er)
