New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong assumption of Chrome exec path on Apple Silicon M1 #6641
Comments
+1 |
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. |
+1 and I almost wanted to remount my root as writable to link the chromium browser binary in /usr/bin. Still not fixed. |
+1 |
We're marking this issue as unconfirmed because it has not had recent activity and we weren't able to confirm it yet. It will be closed if no further activity occurs within the next 30 days. |
What do you need to confirm? |
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! |
I'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
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/
The text was updated successfully, but these errors were encountered: