Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] chromium.executablePath yields null (version 108)

See original GitHub issue

Environment

chromium Version: @sparticuz/chromium @108
puppeteer / puppeteer-core Version: “puppeteer-core”: “19.2.0”
Node.js Version: 14

Expected Behavior

Should yield a path

Current Behavior

chromium.executablePath yields null (version 108)

Issue Analytics

State:
Created a year ago
Comments:7 (6 by maintainers)

Top GitHub Comments

1reaction

paulstelzercommented, Nov 4, 2022

@Sparticuz any idea when you will release it?

0reactions

Sparticuzcommented, Nov 4, 2022

108.0.1 released with this fix

Top Results From Across the Web

Tracking bug for internal fixes: Chrome 108, Release 0

Issue 1394280: Tracking bug for internal fixes: Chrome 108, Release 0. Reported by schedule amyressler@chromium.org amyressler@chromium.org.

[BUG] headless: false & executablePath: null in AWS Lambda

Headless is always false and executablePath is always null. Steps to Reproduce. const chromium = require('chrome-aws-lambda') ...

chrome-aws-lambda/README.md - UNPKG

This will ship with appropriate binary for the latest stable release of [`puppeteer`](https://github.com/GoogleChrome/puppeteer) (usually updated within a day ...

How to resolve failed to download chromium r624492 OS

Solved: I have analysed this function from error log file, async function downloadChromium(options, targetRevision) { console.log(options); ...

mozilla-central: changeset 534188 ...

To use Puppeteer with a different version of Chrome or Chromium, pass in the executable's path when creating a `Browser` instance: ```js ...