[Bug]: Laravel 11

[vitormicillo]

What happened?

When I use the function to generate the pdf, laravel returns this error

The command "PATH=$PATH:/usr/local/bin:/opt/homebrew/bin NODE_PATH=npm root -g node '/Users/user/Development/coral_core2.0/laravel/vendor/spatie/browsershot/src/../bin/browser.cjs' '{"url":"file:\/\/\/var\/folders\/7d\/62pqlypj41zdjk45c94w1x900000gn\/T\/1968630093-0677519001737731718\/index.html","action":"pdf","options":{"args":[],"viewport":{"width":800,"height":600},"displayHeaderFooter":false,"format":"a4","printBackground":true}}'" failed. Exit Code: 1(General error) Working directory: /Users/vitormicillo/Development/coral_core2.0/laravel/public Output: ================ Error Output: ================ node:internal/modules/cjs/loader:1409 const err = new Error(message); ^ Error: Cannot find module 'puppeteer' Require stack: - /Users/vitormicillo/Development/coral_core2.0/laravel/vendor/spatie/browsershot/bin/browser.cjs at Function._resolveFilename (node:internal/modules/cjs/loader:1409:15) at defaultResolveImpl (node:internal/modules/cjs/loader:1060:19) at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1065:22) at Function._load (node:internal/modules/cjs/loader:1214:37) at TracingChannel.traceSync (node:diagnostics_channel:322:14) at wrapModuleLoad (node:internal/modules/cjs/loader:234:24) at Module.require (node:internal/modules/cjs/loader:1495:12) at require (node:internal/modules/helpers:135:16) at callChrome (/Users/vitormicillo/Development/coral_core2.0/laravel/vendor/spatie/browsershot/bin/browser.cjs:70:28) at Object.<anonymous> (/Users/vitormicillo/Development/coral_core2.0/laravel/vendor/spatie/browsershot/bin/browser.cjs:441:5) { code: 'MODULE_NOT_FOUND', requireStack: [ '/Users/vitormicillo/Development/coral_core2.0/laravel/vendor/spatie/browsershot/bin/browser.cjs' ] } Node.js v23.6.0

How to reproduce the bug

This is how I use my function:

` $pdf = Pdf::view('reports.pdf.alert-report', ['record' => $record])
->format('a4')
->download('alert-report.pdf');

    return $pdf;`

the route is very simple too

Route::get('/generate-alert-pdf-report/{id}', [AlertResource::class, 'generatePdfReport'])->name('alert.report.pdf');

Package Version

1.5

PHP Version

8.4.2

Laravel Version

11.9

Which operating systems does with happen with?

macOS

Notes

No response

[Putra-0]

Same, is there any solution?
I am using Ubuntu 24

[djoeycl]

Error: Cannot find module 'puppeteer'

Did you install puppeteer?

[vitormicillo]

Why would I install puppeteer? Shouldn't this be integrated with the library in the same way that dompdf does, right?

[ashtrath]

it does need puppeteer though.
https://spatie.be/docs/laravel-pdf/v1/requirements

Under the hood this package uses Browsershot to generate PDFs. You can find the necessary requirements here.

Under BrowserShot requirement page:

This package requires Node 22.0 (LTS) or higher and the Puppeteer Node library (v23.0 or higher).

[vitormicillo]

Thanks @ashtrath
I will have a try and install puppeteer

[majedqatousa]

can i use laravel-pdf without having npm at my production server !!?

[vitormicillo]

You don't need to, just build the files and send everything.

[michaelpapesch]

well, if you dont want to pollute your git with build files, you should probably think about installing npm on your production server and compile your files there, or you will have to commit new compiled files everytime you change something on your css/js.

[vitormicillo]

well, if you dont want to pollute your git with build files, you should probably think about installing npm on your production server and compile your files there, or you will have to commit new compiled files everytime you change something on your css/js.

I personally do not recommend this; analyzing as DEVOPS the best way and good practices adopted, you should compile, test, and deploy to production.

[michaelpapesch]

I personally do not recommend this; analyzing as DEVOPS the best way and good practices adopted, you should compile, test, and deploy to production.

I don't think you address the issue here.

• Do you put your compiled ressources into git?
  Then what will happen when people try to merge branches with compiled and minified js/css? As far as i know, there is no automagically merging of compiled and minified CSS/JS.

• What is your solution for a workflow with autodeploy and auto merging of pull requests / feature branches?

And in this case specifically: This module uses browserstack, puppeteer and dependencies installed on the server.

• How can you test that on local environment?

The best solution so far for me is building the assets on my pipeline with docker after merging the branches.
But not everyone can do that, and for the most people installing npm on the server and run a npm build is by far the easiest solution.

[MostafaHamedAbdelmasoud]

same issue here! this package was legitimately working with previous Laravel versions!