chromium icon indicating copy to clipboard operation
chromium copied to clipboard

chromium not opening in headful mode

Open sai-sy opened this issue 11 months ago • 1 comments

Environment

I know this was mentioned in issue 38 but it was closed as fixed and am confused as to what I'm doing wrong, I seem to be following the docs exactly

  • puppeteer / puppeteer-core Version:24.0.0
  • Node.js Version: 22

Expected Behavior

chromium browser should've happened

Current Behavior

I think steps are continueing without chromium browser? browser opens (console.log after launch) but business logic times out

Steps to Reproduce

  const browser = await puppeteer.launch({
    args: process.env.IS_LOCAL
      ? puppeteer.defaultArgs().concat([`--proxy-server=${newProxyUrl}`])
      : chromium.args.concat([`--proxy-server=${newProxyUrl}`]),
    defaultViewport: chromium.defaultViewport,
    headless: process.env.IS_LOCAL ? false : chromium.headless,
    //dumpio: true,
    executablePath: process.env.IS_LOCAL
      ? "C:/saiscripts/lib-sub/v4/chromium/win64-1411386/chrome-win/chrome.exe"
      : await chromium.executablePath(),
  });

.env

NODE_ENV=dev
IS_LOCAL=true
  • I don't get "browser was not found" (which I get when switching to my base chrome) so it knows it's there (and knows it is a browser?)

sai-sy avatar Jan 26 '25 08:01 sai-sy

  const browser = await puppeteer.launch({
    args: puppeteer.defaultArgs().concat([`--proxy-server=${newProxyUrl}`]),
    headless: false,
    executablePath: "C:/saiscripts/lib-sub/v4/chromium/win64-1411386/chrome-win/chrome.exe",
  });

does this work? if no, then it's most likely an issue with your chrome version

Sparticuz avatar Jan 27 '25 19:01 Sparticuz