You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 🤷♂️
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.
Info
Type
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 🤷♂️
The text was updated successfully, but these errors were encountered: