fix executablePath (arm64)

[alex2844]

const puppeteer = require('puppeteer-core');
(async () => {
  const browser = await puppeteer.launch({ executablePath: '/usr/bin/chromium' });
  await browser.close();
})();

Error: Failed to launch the browser process! spawn /usr/bin/chromium-browser ENOENT
TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[alex2844]

@googlebot I signed it!

[jackfranklin]

(I'm not familiar with arm64) why would it maybe be in chromium-browser or chromium? Should we update the error message too?

[alex2844]

@jackfranklin The error was updated

[mathiasbynens]

Suggested commit message:

feat: support fetching and launching on Apple M1

Issue: #6495, #6634, #6641, #6614

[mathiasbynens]

@alex2844 Could you please run npm run lint and fix the issues? https://travis-ci.com/github/puppeteer/puppeteer/jobs/465377239#L239-L304

Then we can merge this!

[tylersmalley]

Any way to get movement on this with a release? ❤️

[connorlurring]

Any way to get movement on this with a release? ❤️

+1 for this, willing to help @alex2844 get this over the line if necessary

[google-cla]

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

[alex2844]

@googlebot I consent.

[google-cla]

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

[mathiasbynens]

I’ll go ahead and land this, and will fix any remaining lint issues as a follow-up. Thanks, everyone!

[okonet]

I still have issues installing puppeteer on M1 Mac since it's looking for the the executable to be in /usr/bin/chromium but the the homebrew installation installs packages to /opt/homebrew/bin on Big Sur so it still fails for me. Any suggestions how to resolve it?

[karlhorky]

I added the following to ~/.zshrc as suggested on #6622 (comment)

export PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true
export PUPPETEER_EXECUTABLE_PATH=`which chromium`

...and then used patch-package to modify the puppeteer package:

diff --git a/node_modules/puppeteer/lib/cjs/puppeteer/node/Launcher.js b/node_modules/puppeteer/lib/cjs/puppeteer/node/Launcher.js
index 835c74c..1d6e940 100644
--- a/node_modules/puppeteer/lib/cjs/puppeteer/node/Launcher.js
+++ b/node_modules/puppeteer/lib/cjs/puppeteer/node/Launcher.js
@@ -72,7 +72,7 @@ class ChromeLauncher {
         let chromeExecutable = executablePath;
         if (!executablePath) {
             if (os.arch() === 'arm64') {
-                chromeExecutable = '/usr/bin/chromium-browser';
+                chromeExecutable = '/opt/homebrew/bin/chromium';
             }
             else {
                 const { missingText, executablePath } = resolveExecutablePath(this);

[phcoliveira]

Is there a reason for not using an environment variable before the hardcoded path suggested by Homebrew? Chromium can be installed without using Homebrew, can it not?

chromeExecutable = process.env.CHROMIUM_EXECUTABLE_PATH || '/opt/homebrew/bin/chromium';

[karlhorky]

@phcoliveira, to me this looks great! Want to do a PR and see if the maintainers agree?