Hi all, I know similar questions have been asked a couple of times in here but I'm a bit stuck on getting

chrome-aws-lambda

and puppeteer working with local sst start. I've tried various combinations of bundle options including

nodeModules

and

externalModules

and

copyFiles

but nothing seems to work and the

nodeModules

and

copyFiles

settings seem to have no effect on what ends up in the artifact file when running via

sst start

. I've also tested out the example at https://github.com/serverless-stack/serverless-stack/tree/master/examples/layer-chrome-aws-lambda and get the same error of

Cannot find module 'chrome-aws-lambda'

If I remove

chrome-aws-lambda

from the

externalModules

setting then there is a different error

Cannot find module ...<path omitted>/backend/functions/puppeteer/lib/Browser

The readme in the example makes it seem like it should work with

sst start

but it doesn't seem to.

Hi @Dan Coates, with version of SST are you using? I have it working locally without problems,

Hi @outaTiME I'm using sst 1.1.2

great, this is my (partial) package.json:

"dependencies": {
  "@serverless-stack/cli": "1.1.2",
  "@serverless-stack/resources": "1.1.2",
  "aws-cdk-lib": "2.24.0",
  "chrome-aws-lambda": "^10.1.0",
  "puppeteer-core": "^10.1.0",
},
"devDependencies": {
  "puppeteer": "^10.1.0"
}

this is the definition on my stack:

socialNotify: {
  function: {
    handler: 'src/subscribers/social-notify.handler',
    bundle: {
      externalModules: ['chrome-aws-lambda'],
    },
    layers: ['arn:aws:lambda:us-east-1:764866452798:layer:chrome-aws-lambda:25'],
    // ~30s
    timeout: '1 minute',
  },
  cdk: {
    subscription: {
      filterPolicy: {
        event: SubscriptionFilter.stringFilter({
          allowlist: ['social-notify'],
        }),
      },
    },
  },
},

finally, you can check my lambda here: https://github.com/outaTiME/ambito-dolar/blob/master/packages/api/src/subscribers/social-notify.js side note, that’s my app’s productive repository that uses SST 0.69 but the lambda stays intact for SST 1.x, hope it helps 🙏

Thanks @outaTiME I really appreciate you taking the time to put together the example. I suspect the difference is that you are using sst in the same package as your application code. We keep our infra code separate from the application code similar to how the example is set up: https://github.com/serverless-stack/serverless-stack/tree/master/examples/layer-chrome-aws-lambda

hey @Dan Coates have you followed this tutorial? https://serverless-stack.com/examples/how-to-use-lambda-layers-in-your-serverless-app.html

Hey @manitej yep, I've followed that step by step and get the exact same errors.

locally not working?

that is correct

@outaTiME thanks for helping out 🙌

Hi Frank, thanks for the message, I have actually already tried that example. I'm curious if it works for anyone else? Unless I'm missing some steps or requirements it seems like it wouldn't work because

chrome-aws-lambda

is marked as an externalModule in the stack config, and even if you remove that, you get the

Cannot find module ...<path omitted>/backend/functions/puppeteer/lib/Browser

error I mentioned above.

Ah I was having this same exact issue as @Dan Coates

Did you manage to resolve it @Tony J?