-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
Upgrade puppeteer #6480
Comments
on it! |
actually we are running on chrome-stable that travis gives us as we skip Puppeteer download. i'll upgrade puppeteer nevertheless
looking at travis logs we're on chrome 70
|
@wardpeet oh that's true. well locally we use pptr's chromium, which is a bit old. |
Hello. Excuse-me; starting this:
|
@kud this dependency update was just for development dependencies. Lighthouse CLI uses whatever Chrome is found installed on your machine (see https://github.com/GoogleChrome/chrome-launcher/blob/master/src/chrome-finder.ts). |
Thank you @patrickhulce :) Do you think it's possible to specify a particular browser like I can do on
https://github.com/garris/BackstopJS#chrome-headless-the-latest-webkit-library |
You can set an environment variable called |
Thank you @wardpeet but it would be applied on any project/tool which needs a chrome, no? |
Not exactly. Everything that uses Chrome Launcher under the hood would. For example puppeteer doesn't because it has it's own mechanism. You can define a custom path |
Oh! Okay, thank you. :) |
We're rocking a chrome that's a few months old.
Let's bump up to latest!
The text was updated successfully, but these errors were encountered: