Chromium not found when running Yarn

[drguthals]

After cloning the repo and installing node and yarn (as described in the contributing guide), I ran yarn and received a similar error to this:

The chromium binary is not available for arm64:
If you are on Ubuntu, you can install with:

 apt-get install chromium-browser

path-to-project/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserFetcher.js:112
            throw new Error();

I found some information on how to possibly resolve this here, which suggested that the issue was that chromium might not be allowed to open on the new M1. So they suggest:

1. Install chromium with Homebrew:
   brew install chromium
2. Open chromium and you should get a popup error saying that it cannot be opened because the developer cannot be verified.
3. Go into your System Preferences and allow chromium to be opened (under Security & Privacy -> General)
4. Close and open your terminal and try again

I tried this (several times) but received a different popup error saying that my chromium was damaged. Even though I uninstalled/reinstalled chromium many times (and tried re-starting my terminal and re-starting my computer) it was still causing the issue.

I then tried:

1. Uninstall chromium
2. Install chromium with: brew install chromium --no-quarantine

You can find this described here, but the instructions here were referenced, which didn't seem to help in my situation.

In any case, it seems like whether you're getting a "damaged" or "unknown developer" popup error when installing/running chromium, it is the "same" issue.

Note:
In my System Preference -> Security & Privacy -> General, it is already set to Allow apps downloaded from: Anywhere

After running:

brew uninstall chromium
brew install chromium --no-quarantine

And then restarting my terminal and rerunning yarn - it works!

Started this discussion to ask

Should we add some information to our CONTRIBUTING.md file, or is this a very rare case?

[AbhiPrasad]

Hey @drguthals - I think this is worth adding a note to CONTRIBUTING.md.

It's kind of annoying that this even happens, so I opened two issues #6054 and #6053 to track removing puppeteer usage in general, which should lead to folks not needing to even install chromium to get things working.

[drguthals]

I will open a PR to add a note to CONTRIBUTING.md

Thanks @AbhiPrasad