Try switching to Docker target, toggle Redis to off.
Then try adding a local dev target.
And then, you can follow Ken’s tutorial to setup Redis externally.
I manage to solve it, thanks both @sid (as always) and @mebeingken
Here is what I did:
Used docker to deploy a Redis server inside it, binding docker’s inner port to my Mac (using port 3350) in order to make Redis available for my NodeJS app.
Changed the target to local NodeJS and then configured redis on wappler
Yeah… I can’t believe it, but I was struggling to create PDFs using Wappler and once an option appears (thanks @sid for that), I’m having all this trouble to make it work…
Besides PDF creation, Puppeteer is an excellent module for my app. Hope it’s worth it…
We have just added Puppeteer to a Docker Project running Node, and its dependencies, with no issues (on Windows 10). So not sure what happened with your Project @salvuccicarlos? Attached terminal output below:
message: "Failed to launch the browser process!\n/opt/node_app/node_modules/puppeteer/.local-chromium/linux-869685/chrome-linux/chrome: error while loading shared libraries: libgobject-2.0.so.0: cannot open shared object file: No such file or directory\n\n\nTROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md\n"
stack: "Error: Failed to launch the browser process!\n/opt/node_app/node_modules/puppeteer/.local-chromium/linux-869685/chrome-linux/chrome: error while loading shared libraries: libgobject-2.0.so.0: cannot open shared object file: No such file or directory\n\n\nTROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md\n\n at onClose (/opt/node_app/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:194:20)\n at Interface. (/opt/node_app/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:184:68)\n at Interface.emit (events.js:326:22)\n at Interface.close (readline.js:416:8)\n at Socket.onend (readline.js:194:10)\n at Socket.emit (events.js:326:22)\n at endReadableNT (_stream_readable.js:1241:12)\n at processTicksAndRejections (internal/process/task_queues.js:84:21)"
status: "500"
Are you just installing the core Puppeteer package or trying to install Puppeteer and its Chrome component? We just used the core has have no need for the full Chrome version… May be where the issue is?