Wrong assumption of Chrome exec path on Apple Silicon M1
See original GitHub issueI’ll make this as short as possible since it’s very straightforward (I bet you like it this way for this particular issue)
In Launcher.js:79
let chromeExecutable = executablePath;
if (os.arch() === 'arm64') {
chromeExecutable = '/usr/bin/chromium-browser';
}
else if (!executablePath) {
The path provided to puppeteer is: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
I’m using ARM64 Node.js v15 compiled by this link: https://www.reddit.com/r/apple/comments/jyfg4m/nodejs_running_native_on_apple_silicon_m1_mac_mini/
Issue Analytics
- State:
- Created 3 years ago
- Reactions:18
- Comments:8
Top Results From Across the Web
Chrome not giving option for m1 version - Apple Community
I'm trying to load Google Chrome onto my macbook air with m1 chip and it isn't giving me the option to load the...
Read more >How to set up an M1 MacBook for web development
In this tutorial, we set up web development tools for our MacBook in just 20 minutes, including Git, GitHub, VS Code, and Powerline...
Read more >OSX fix Selenium Chromedriver launch error spawn ...
Root Cause: The ChromeDriver team added "_m1" to the end of the filename for their Apple Silicon ARM builds of Chromedriver -- but...
Read more >Install Ubuntu Desktop 22.04 ARM64 on macOS Apple ...
So I have to assume that the installation fails/hangs. Is there any special setting that ... Be on a M1 Mac - I'm...
Read more >Page 16 – #! is not a curse word
This summary isn't quite as big as last week's, but very close. This week many people got their hands on the first Macs...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Thanks for pointing us all in the right direction, @kenny-y!
👆 I patched it directly in my node_modules folder. Will do until an official fix comes out.
We are closing this issue. If the issue still persists in the latest version of Puppeteer, please reopen the issue and update the description. We will try our best to accomodate it!