Skip to content
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

Support Mac OS M1 arm64 #16

Closed
homanp opened this issue Feb 26, 2021 · 4 comments
Closed

Support Mac OS M1 arm64 #16

homanp opened this issue Feb 26, 2021 · 4 comments
Labels
question Further information is requested

Comments

@homanp
Copy link

homanp commented Feb 26, 2021

Describe the bug
When trying to install this package on a Mac M1 arm64 I get the following error:

The chromium binary is not available for arm64

To Reproduce
Steps to reproduce the behavior (Mac M1):

  1. Run npm i crittr

Expected behavior
Package should install

Screenshots
Screenshot 2021-02-26 at 10 07 18

Environment (please complete the following information):

  • OS: Mac M1
  • Version 11.2
@philipp-winterle
Copy link
Owner

@homanp thx for providing this issue.
Iam affraid this is not an issue which crittr is responsible for. As far as my research is valid it should be gone with nodejs 14 and only occur with nodejs 15. Because nodejs 15 is already build for ARM and so it needs to install the arm version of chrome aswell.
See more info here: puppeteer/puppeteer#6622 (comment)

So in short this is most likely a chromium or a puppeteer issue. We have to wait till they fix it. As an alternative you could try to install chromium on your own as described above "sudo apt install chromium" and set the ENV Flag "PUPPETEER_SKIP_CHROMIUM_DOWNLOAD" to true I guess. So it will skil the install and use the current available chromium browser. You may give it a try.
But keep in mind that this will be reverted on the next update and install of crittr. As long as there is no fixed set "PUPPETEER_SKIP_CHROMIUM_DOWNLOAD" Flag, it will install the puppeteer version of chrome the next time. Then hopefully working.

TL;DR: no crittr issue. Will be fixed by either the googlechrome crew or puppeteer uses a workarround and I need to raise it to 8.x.

@philipp-winterle philipp-winterle added the question Further information is requested label Feb 26, 2021
@homanp
Copy link
Author

homanp commented Feb 26, 2021

@hummal yep you are correct :)

Thanks for the swift response!

@philipp-winterle
Copy link
Owner

You're welcome. :) Hope it is working for you again

@philipp-winterle
Copy link
Owner

https://github.com/puppeteer/puppeteer/releases/tag/v9.0.0

After the upgrade to puppeteer 9.0.0 Mac M1 should work as expected without workarrounds

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants