#52690 closed defect (bug) (fixed)
`npm install` aborts on Apple Silicon due to Puppeteer not finding appropriate chromium binary
Reported by: | afragen | Owned by: | gziolo |
---|---|---|---|
Milestone: | 6.0 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Build/Test Tools | Keywords: | has-patch |
Focuses: | Cc: |
Description
On Apple Silicon, I get an error running npm install
from wordpress-develop
due to a puppeteer script.
$ npm install > puppeteer@4.0.1 install /Users/afragen/Local_Beta_Sites/wordpressdevelop/app/public/node_modules/grunt-contrib-qunit/node_modules/puppeteer > node install.js The chromium binary is not available for arm64: If you are on Ubuntu, you can install with: apt-get install chromium-browser /Users/afragen/Local_Beta_Sites/wordpressdevelop/app/public/node_modules/grunt-contrib-qunit/node_modules/puppeteer/lib/BrowserFetcher.js:112 throw new Error(); ^ Error at /Users/afragen/Local_Beta_Sites/wordpressdevelop/app/public/node_modules/grunt-contrib-qunit/node_modules/puppeteer/lib/BrowserFetcher.js:112:19
I am running the shell session in Rosetta (x86_64) emulation. This has previously worked and not certain if it's related to r50441.
Setting export PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true
in the session does allow for the npm install
to complete.
Change History (9)
#3
@
4 years ago
I have used nvm
to install node v15.x which is able to be compiled for arm64. Must have Xcode Command Line Tools installed.
nvm install 15
, give this time to compile/build, currently this installs node v15.10.0nvm use 15
nvm alias default 15
, this so every new session will use this version of node.
Now there's no need to run the shell session under Rosetta.
This ticket was mentioned in PR #2509 on WordPress/wordpress-develop by gziolo.
3 years ago
#5
- Keywords has-patch added
Trac ticket: https://core.trac.wordpress.org/ticket/52690
There is a brand new version grunt-contrib-qunit
that resolves the issue with Puppeteer's installation.
#7
@
3 years ago
- Owner set to gziolo
- Resolution set to fixed
- Status changed from new to closed
In 53069:
3 years ago
#9
Committed with https://core.trac.wordpress.org/changeset/53069.
Upstream issue with some workaround: https://github.com/puppeteer/puppeteer/issues/6622