How to do this specific thing with the npm module pupeteer?

According to https://stackoverflow.com/questions/52993002/headless-chrome-node-api-and-puppeteer-installation, the way to fix chromium not launching is by running this command:

sudo apt-get install gconf-service libasound2 libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgcc1 libgconf-2-4 libgdk-pixbuf2.0-0 libglib2.0-0 libgtk-3-0 libnspr4 libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-6 libx11-xcb1 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxext6 libxfixes3 libxi6 libxrandr2 libxrender1 libxss1 libxtst6 ca-certificates fonts-liberation libappindicator1 libnss3 lsb-release xdg-utils wget

However, the console says sudo is not a command and if I remove sudo, it says I don’t have permission. I am completely unfamiliar with consoles. I have no idea what kind of solution is needed here, but I’m sure you guys know something I don’t.

EDIT: https://glitch.com/edit/#!/os-ogg is the project if you want to look at it

1 Like

try curl -l https://api.glitch.com/v1/uptime
from what i know, it will provide your uptime/launcher info, if chromium does not launch, u should see something like chromium: 404 i think

nope, removed, the uptime is removed, ignore this

ok, do this:
yarn i puppeteer -D
if error do this:
yarn update puppeteer

1 Like

yarn: command not found

do npm i yarn && yarn i puppeteer -D

1 Like

It’s actually “yarn upgrade”, but pupeteer still errors even after upgrading. Thanks anyways.

As far as I know, Puppeter will cause problems like and this.

1 Like