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

NPM Install fails: The chromium binary is not available for arm64 #687

Open
1 of 2 tasks
tjex opened this issue Oct 10, 2023 · 1 comment
Open
1 of 2 tasks

NPM Install fails: The chromium binary is not available for arm64 #687

tjex opened this issue Oct 10, 2023 · 1 comment

Comments

@tjex
Copy link

tjex commented Oct 10, 2023

Info

  • Operating System: OSX Ventura 13.5
  • Node Version: 20.5.1

Type

  • bug
  • feature request

For Bugs

running npm i --verbose fusuma -D results in errors:
The errors relate to a chromium binary not being available.
I shouldn't have to have a chromium binary on my system to run this in the first place I would think?

Installing with yarn results in the same error.
But ... installing with bun works, and running it too 🤷‍♂️

npm verb Darwin 22.6.0
npm verb node v20.5.1
npm verb npm  v10.2.0
npm ERR! code 1
npm ERR! path /Users/tjex/docs/presentations/ctech_pr-2023-10/node_modules/puppeteer
npm ERR! command failed
npm ERR! command sh -c node install.js
npm ERR! The chromium binary is not available for arm64.
npm ERR! If you are on Ubuntu, you can install with:
npm ERR!
npm ERR!  sudo apt install chromium
npm ERR!
npm ERR!
npm ERR!  sudo apt install chromium-browser
npm ERR!
npm ERR! /Users/tjex/docs/presentations/ctech_pr-2023-10/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserFetcher.js:115
npm ERR!                     throw new Error();
npm ERR!                     ^
npm ERR!
npm ERR! Error
npm ERR!     at /Users/tjex/docs/presentations/ctech_pr-2023-10/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserFetcher.js:115:27
npm ERR!     at FSReqCallback.oncomplete (node:fs:200:21)
npm ERR!
npm ERR! Node.js v20.5.1
npm verb exit 1
npm verb unfinished npm timer reify 1696950551613
npm verb unfinished npm timer reify:build 1696950556488
npm verb unfinished npm timer build 1696950556489
npm verb unfinished npm timer build:deps 1696950556490
npm verb unfinished npm timer build:run:install 1696950556512
npm verb unfinished npm timer build:run:install:node_modules/puppeteer 1696950556512
npm verb unfinished npm timer build:run:install:node_modules/pa11y/node_modules/puppeteer 1696950556516
npm verb unfinished npm timer build:run:install:node_modules/watchpack-chokidar2/node_modules/fsevents 1696950556517
npm verb code 1
@tjex
Copy link
Author

tjex commented Oct 10, 2023

Bun fails to build the project, and references the same module as npm / yarn does originally. Pupeteer.

Error: Failed to launch the browser process! spawn /usr/bin/chromium-browser ENOENT

    at onClose (/Users/tjex/docs/presentations/ctech_pr-2023-10/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:193:20)
    at ChildProcess.<anonymous> (/Users/tjex/docs/presentations/ctech_pr-2023-10/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:185:85)
    at ChildProcess.emit (node:events:514:28)
    at ChildProcess._handle.onexit (node:internal/child_process:292:12)
    at onErrorNT (node:internal/child_process:484:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
error: "fusuma" exited with code 1 (SIGHUP)

So it's again down to the chromium-browser not being installed...
The readme states that we can use Chrom or Firefox. So I'm not sure what's going on.

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

No branches or pull requests

1 participant