hi again guys, I am not able to get

chrome-aws-lambda

working with

nodejs16.x

when I deploy it (locally it works without problems), did anyone get it? If I use version 14 of node it works perfectly, I attach the error message:

"Failed to launch the browser process!\n/tmp/chromium: error while loading shared libraries: libnss3.so: 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!",
        "/tmp/chromium: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory",
        "",
        "",
        "TROUBLESHOOTING: <https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md>",
        "",
        "    at onClose (/opt/nodejs/node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserRunner.js:193:20)",
        "    at Interface.<anonymous> (/opt/nodejs/node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserRunner.js:183:68)",
        "    at Interface.emit (node:events:532:35)",
        "    at Interface.close (node:readline:586:8)",
        "    at Socket.onend (node:readline:277:10)",
        "    at Socket.emit (node:events:532:35)",
        "    at endReadableNT (node:internal/streams/readable:1346:12)",
        "    at processTicksAndRejections (node:internal/process/task_queues:83:21)"

Maybe https://github.com/alixaxel/chrome-aws-lambda / https://github.com/shelfio/chrome-aws-lambda-layer doesn’t support node 16 yet? 🤔 If you try to deploy the example (https://github.com/serverless-stack/serverless-stack/tree/master/examples/layer-chrome-aws-lambda) you will see the error that I am telling you

@outaTiME if you are trying to depoy it via Seed auto deployment, the Seed only works up to the nodejs14.x

Hi @Meris Tarhanis, I am deploying it manually, at the moment to solve it I configure that only that function runs with

nodejs14.x

😪

Well you did find a solution for that 😄, a shame that you can't reap the benefits of auto deployment, but from their last Stream, I caught the talk that they are working on integrating node16.x support into the Seed as well.

yeah, as I said before, this seems to be a problem with one of these dependencies: https://github.com/alixaxel/chrome-aws-lambda / https://github.com/shelfio/chrome-aws-lambda-layer

A side note, @Meris Tarhanis u can pin a specific node version in your seed.yml buildsped https://seed.run/docs/adding-a-build-spec.html#customizing-node-versions

@Frank I didn't know that, but thank you as that will fix some future problems we might have