LIGHTHOUSE_CHROMIUM_PATH can be identified automatically on Linux
See original GitHub issueHaving Chrome/Chromium installed on Linux typically means that there are *.desktop
files corresponding to installed application.
Global files are likely located as /usr/share/applications/*.desktop
and local to user as ~/.local/share/applications/*.desktop
.
So in most cases it is possible to scan files at those directories and try to find something with /chrome
in Exec
key. This wouldn’t work in case when Chromium was extracted into some directory and no desktop file was created, but otherwise it might improve convenience of using lighthouse by not requiring to specify LIGHTHOUSE_CHROMIUM_PATH
explicitly (which is boring).
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Lighthouse overview - Chrome Developers
Lighthouse is an open-source, automated tool for improving the quality of web pages. You can run it against any web page, ...
Read more >Running Lighthouse Reports on the Command Line - Medium
This blog post shows you how to run Google Lighthouse on the command line and how to customize the reports. After reading this...
Read more >lighthouse - npm
Lighthouse analyzes web apps and web pages, collecting modern performance metrics and insights on developer best practices. Using Lighthouse.
Read more >Performance monitoring with Lighthouse CI - web.dev
For example, the autorun command executes multiple Lighthouse runs, identifies the median Lighthouse report, and uploads the report for storage.
Read more >Lighthouse - GitHub Pages
Lighthouse Linux Build Status Windows Build Status Coverage Status NPM ... By default, any detected Chrome Canary or Chrome (stable) will be launched....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@jeanleonino thanks we have a pr open that fixes this issue without setting the chromium path. (#856)
will have a look on a vm with a few distros