Usage of puppeteer-core with puppeteer-extra

[photorealisticbeaver]

Starting on puppeteer 19, PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true seems to be ignored, so it would be quite handy to be able to use puppeteer-core with puppeteer-extra

[ushuz]

puppeteer-core is supported https://github.com/berstend/puppeteer-extra/blob/39248f1f5deeb21b1e7eb6ae07b8ef73f1231ab9/packages/puppeteer-extra/src/index.ts#L534-L538

[photorealisticbeaver]

@ushuz sorry, but still getting this on a clean build, under node_modules/puppeteer-extra/dist/index.d.ts

currently with:

• puppeteer-core 19.11.1
• puppeteer-extra 3.3.6
• puppeteer-extra-plugin-stealth 2.11.2

PS - also getting this from node_modules/puppeteer-extra-plugin/dist/(puppeteer.d.ts

[massenandev]

@photorealisticbeaver were you able to use puppeteer-core with puppeteer-extra?

[photorealisticbeaver]

@massenandev not really, no

[AdrKacz]

Any updates? How would you use puppeteer-extra when you don't want to install the browsers with puppeteer?

[Rusty-b0lt]

Any updates? Trying to use puppeteer-extra with @sparticuz/chromium. So I need only puppeteer-core.

[photorealisticbeaver]

@AdrKacz @Rusty-b0lt I wasn't able to put it to work, and haven't tried again. I stayed with the latest v18, where you could use PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true

@ushuz anything that I was missing, for it not to work with puppeteer-core?

[BaptisteDri]

@Rusty-b0lt @AdrKacz did you find any solution ? I'm trying to use puppeteer-extra with @sparticuz/chromium-min and puppeteer-core

[mbrevda]

Seems puppeteer is installed by default by puppeteer-extra. It would be helpful to be able to pass in an instance of puppeteer and not have this package install it by default.

npm ls puppeteer   
[email protected] PATH_TO_PROJECT
└─┬ [email protected]
  └── [email protected]

[Rusty-b0lt]

@BaptisteDri no solutions found:( im also trying to use with @sparticuz/chromium in aws lambda, maybe i really should just downgrade to v18

[ford-jones]

@Rusty-b0lt

I'm able to run @sparticuz/chromium with puppeteer-extra: "^3.3.6" inside of aws-lambda by setting this environment variable: PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=1 and passing the following configuration into puppeteer:

import puppeteer from "puppeteer-extra"
import Chromium from "@sparticuz/chromium"

export const PuppeteerConfig = async () => {
    return await puppeteer.launch({
      executablePath: await Chromium.executablePath(),
      headless: true,
      ignoreHTTPSErrors: false,
      args: [...Chromium.args, "--incognito", "--no-sandbox"]
    })
}

Edit: The issue I've found with this method is that the plugins which are enabled by puppeteer-extra expect puppeteer's default Chrome version to be installed to it's default location. As far as I can tell, none of these plugins have any such configuration options available which allow us to point the plugin to our own version of chromium.