-
Notifications
You must be signed in to change notification settings - Fork 629
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
The puppeteerLaunchOptions seems not working #947
Comments
I am experiencing the same issue when passing |
Same for me. |
Still and issue, anyone looking at this? |
it works with cli option lighthouse-ci/docs/configuration.md Line 206 in 6914f5b
it has preference over puppeteerLaunchOptions: lighthouse-ci/packages/cli/src/collect/puppeteer-manager.js Lines 61 to 68 in 6914f5b
|
Describe the bug
![Screenshot 2023-10-09 at 10 59 44 AM](https://private-user-images.githubusercontent.com/60414595/273476031-0b5415ce-33aa-4215-a45d-7726d34399a7.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTkwNTU5ODMsIm5iZiI6MTcxOTA1NTY4MywicGF0aCI6Ii82MDQxNDU5NS8yNzM0NzYwMzEtMGI1NDE1Y2UtMzNhYS00MjE1LWE0NWQtNzcyNmQzNDM5OWE3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MjIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjIyVDExMjgwM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTRhODhlMjUyYTdjZWFjY2M4YWUyMTAxNDI1ZTk5MGRkOGM2ZDkwODQwYWUzNTBhOGVkODI3ODg0MWFlMzRkNmUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.SEi-OeWH1ypN5u80aAEbKW8480LC4hspaxONEnfgUpw)
I suspect the puppeteerLaunchOptions is not working because I passed "new" to the headless option, and I still get the headless deprecation warning. I also tried passing false to it, and getting the same warning and there was no chrome instance launched.
To Reproduce
And setting up puppeteer-script.js.
Expected behavior
I'm expecting when I set the headless to be false, after run
lhci collect
, a chrome browser gets launched so that I can debug the log in steps.The text was updated successfully, but these errors were encountered: