Closed yixuanhou closed 1 week ago
I am experiencing the same issue when passing { headless: "new" }
to puppeteerLaunchOptions
. The old headless deprecation warning still appears.
Same for me.
Still and issue, anyone looking at this?
it works with cli option headful
https://github.com/GoogleChrome/lighthouse-ci/blob/6914f5be825ea23e09edcd5cb46660b06dc38100/docs/configuration.md?plain=1#L206
it has preference over puppeteerLaunchOptions: https://github.com/GoogleChrome/lighthouse-ci/blob/6914f5be825ea23e09edcd5cb46660b06dc38100/packages/cli/src/collect/puppeteer-manager.js#L61-L68
Describe the bug 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.![Screenshot 2023-10-09 at 10 59 44 AM](https://github.com/GoogleChrome/lighthouse-ci/assets/60414595/0b5415ce-33aa-4215-a45d-7726d34399a7)
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.