Compatability with Puppeteer 19?

[mo-rocks]

Puppeteer 19 downloads Chromium into a .cache folder, previously it stored it within it's own node_modules folder. For some reason Browsershot won't work anymore with this, I get the error 'Could not find expected browser locally'.

[ridxery]

I faced the same problem upgrading, tried to set Chrome path manually but none seemed to worked out so reverted it back and use older version of puppeteer right now, will try again later on

[iFlyinq]

What version have you reverted back to? I can't seem to find a version that is working at all

[ridxery]

puppeteer@13.1.1 was my old version, reverted it back everything working fine using browsershot@3.57.2

[ethanclevenger91]

Puppeteer 19 moved the directory the Chrome binary gets stored in. The Browsershot requirements installation instructions will need to be updated.

Oddly, however, I've found that even in version 18, .local-chromium is not where Browsershot's requirements instructions expect it to be.

You can either fiddle with the chmod command in the requirements instructions, change Puppeteer's cache directory, or revert to v17. Your environment will probably dictate which routes are viable for you. I didn't want to futz with configuring the install directory, and in my Laravel Sail setup I couldn't even cd into the default directory where the new binary is supposed to be installed to - probably related to this. So I ended up reverting to v17:

curl -sL https://deb.nodesource.com/setup_14.x | sudo -E bash -
sudo apt-get install -y nodejs gconf-service libasound2 libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgbm1 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 libgbm-dev libxshmfence-dev
sudo npm install --location=global --unsafe-perm puppeteer@^17
sudo chmod -R o+rx /usr/lib/node_modules/puppeteer/.local-chromium

Should get you up and running again.

[RalpinMcDjango]

Forge is definitely impacted. The instructions in the doc site do not work on my production forge server. However the instructions you posted about with v17 do work.

I second this. I've just provisioned a Ubunutu 22 server through Laravel Forge and the provided install steps do not work anymore this suggested fix has made it possible to install browser shot

[freekmurze]

Feel free to send a PR to the docs with working instructions for Forge. Thanks!

[kokoshneta]

For the record, I had the issue when trying to install on a Windows Server 2019 as well (asked about it on Laracasts a few months back before finding this thread). No Forge, Sail or Docker involved at all there, just a simple install directly from the command prompt on the server.

The executable is correctly downloaded and installed into ~/.cache/puppeteer, but Puppeteer seems to be looking in C:\Windows\system32\config\systemprofile\.cache\puppeteer instead.

[neppoz]

The suggested solution from @ethanclevenger91 is working also for me on a 22.04 Ubuntu server.

I would suggest to update the requirements section of the site. Me personally struggled 3 hours figuring out because it was not working. I considered these instructions -> https://spatie.be/docs/browsershot/v2/requirements

[Baspa]

Followed these steps but stil get this error message: chmod: cannot access '/usr/lib/node_modules/puppeteer/.local-chromium': No such file or directory. Seems my location is: /usr/local/lib/node_modules/puppeteer/.local-chromium.

[booni3]

I was unable to get this working using the forge install instructions. Specifically, the issue was on the last command:

$ sudo chmod -R o+rx /usr/lib/node_modules/puppeteer/.local-chromium
> chmod: cannot access '/usr/lib/node_modules/puppeteer/.local-chromium': No such file or directory

My workaround was to install puppeteer & chromium globally. Puppeteer via NPM and chromium via apt-get.

$ sudo npm install -g puppeteer
$ sudo apt-get install chromium-browser

Then in Browsershot, specify the chromium bin. You can use which chromium to find the location

Browsershot::url('https://google.com')
    ->setChromePath('/snap/bin/chromium')
    ->bodyHtml()

I tried a few other things prior to this including:

• Installing puppeteer and chromium via npm, manually specifying all paths/bins.
• Downgrading puppeteer and global installing with npm
• The forge puppeteer instructions
• Installing puppeteer at the project level. This actually did work right away without any messing around, but I preferred to install it globally in this case.

[Baspa]

What version of Puppeteer are you using? I am still getting the following error: Error: Cannot find module '/home/forge/<domainname>/vendor/spatie/browsershot/bin/browser.js'

[Baspa]

For future readers with the same problems: I had to terminate Horizon to fix my issue.

[minutiae]

Another way I found to make it work with Puppeteer 20.x when installed globally, if you want a more fixed Chromium install than installing it via apt-get:

1. Show dir where npm installs packages globally:
   npm list -g

2. Referencing that directory, append node_modules/puppeteer/install.js to get the path to the install file. Run it:
   node <path from step 1>/node_modules/puppeteer/install.js

You should see some output that it's downloading Chrome.
When complete it will give you the path to Chrome.

3. Based on the output of that command, run the permissions change
   from the original instructions in this package to target the binary (what's appended to the path may change in a future version, take a look in yours to find out if needed):
   sudo chmod -R o+rx <path from step 2>/chrome-linux64/chrome

4. Call browsershot with ->setChromePath() pointing to that same path.

[aeq-dev]

Hi @minutiae
I followed your steps but still doesn't work,
Ubuntu 22
npm 9.5.1
node v18.16.0
puppeteer 20.4.0
Laravel 10

Here's my post :
#736

[minutiae]

The error message mentions a snap path. When I went through the steps I posted, mine didn't install via snap.
the path is more like /home/forge/.cache/puppeteer/chrome/linux-113.0.5672.63/chrome-linux64/chrome

If at some point you ran sudo apt-get install chromium-browser to install chromium (which does use snap in my setup), I'd try uninstalling that, repeating my steps, then see if the chrome binary is installed in something more like the path above.

[aeq-dev]

Thanks for reply,
In fact it's same with me,
/home/ubuntu/.cache/puppeteer/chrome/linux-113.0.5672.63/chrome-linux64/chrome
So, should I set :
->setChromePath("/home/ubuntu/.cache/puppeteer/chrome/linux-113.0.5672.63/chrome-linux64/chrome");

[aeq-dev]

Could you please help me for this issue :)

[colinmackinlay]

@ethanclevenger91 solution worked fine for me too on recently provisioned forge server. @freekmurze I've created a pull request #777 to update the docs

[ryanmortier]

Puppeteer is up to v21 now. Are we forever constrained to v17 or does anyone know a solution to use updated versions?

I've tried setChromePath() without success.

[lkmadushan]

Same problem here...

[wardhache]

For me, freezing the chromium installation to a different path worked. Know that I work using a docker container using Debian 11.
I installed chromium and placed it in a different directory (like /tmp/chromium/). Originally, you can find the installed files in /usr/lib/chromium

I've placed chromium version 120.0.6099.199 there this way. Then I've updated puppeteer to version 21.7.0.

Now, in my Dockerfile, we have the following in place:

ENV PUPPETEER_EXECUTABLE_PATH=/tmp/chromium/chromium
ENV PUPPETEER_SKIP_DOWNLOAD=1
...
RUN npm install --global --unsafe-perm puppeteer@21.7.0

It looks like I've got it working this way. Setting the skip download variable like this prevents puppeteer to download chromium and it will use the path I've provided.

Hopefully this can help somebody

[HS-cvift]

the problem is: puppeteer is installed as root, so the browser is located in/root/ and not accessible with the forge user
the solution is simple.

skip
curl -sL https://deb.nodesource.com/setup_14.x | sudo -E bash -
because the forge server had already node installed (currently v18)

install dependencies für chrome:
sudo apt-get install -y nodejs gconf-service libasound2 libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgbm1 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 libgbm-dev libxshmfence-dev (same as documentation)

now install puppeteer as forge user
assumed: you are in the project folder, you are not using ci (vite/other node stuff)
npm install puppeteer

if you are using ci/vite/other node stuff, add puppeteer in your package.json and use "npm ci" in your deployment script. don't remove the node modules :)

that is all.

someone should update the documentation

[Xoshbin]

Did anyone able to make it work, for the past year that is the fourth time I'm trying to update Puppeteer, but each time I have to downgrade it again. It's working on Laravel sail, but on production on Runcloud it's giving errors.

[benholmen]

I just installed this and thought I'd share what worked for me:

curl -sL https://deb.nodesource.com/setup_22.x | sudo -E bash - # pick your nodejs version here, I chose v22 as it's the current

sudo apt-get install -y nodejs gconf-service libasound2 libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgbm1 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 libgbm-dev libxshmfence-dev

sudo npm install --location=global --unsafe-perm puppeteer

npx puppeteer browsers install chrome

This allowed me to install the latest version of Puppeteer (v22.6.5) and Chrome (v123.0.6312.122) on a typical Forge setup.

[cornelRaiu]

If you want to use it on Vagrant with Homestead

sudo apt-get install -y nodejs gconf-service libasound2 libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgbm1 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 libgbm-dev libxshmfence-dev

sudo npm install --location=global --unsafe-perm puppeteer

npx puppeteer browsers install chrome

And then, in PHP:

$html = '<div>test image from section markup</div>';

Browsershot::html( $html )
    ->setChromePath( '/snap/bin/chromium' )
    ->setCustomTempPath( storage_path() )
    ->save(storage_path('app/public') . '/img.png');

it works with puppeteer@22.7.1 and Chrome v124.0.6367.78 .