Marco Lüthy

@vladgolubev we don't have to worry about the response payload limit (or any APIG limits) since we never respond with anything Chrome-related from the Lambda function's `callback()`. Currently, everything is...

There's a similar thread in https://github.com/adieuadieu/serverless-chrome/issues/17. It is [possible](https://twitter.com/adieuadieu/status/862345494646800384) to do this both locally and on Lambda. But as @shaeqahmed notes, it's not exactly straightforward. CDPs `Page.startScreencast` will trigger a...

Hi @ppcano — yes of course we'd welcome a PR! The challenge with `chrome-har-capturer` would be figuring out how it best fits (if at all) into Chromeless. Behind the scenes,...

Hi @neekolas yes of course! You're right that we haven't documented this very well, but Chromeless can be used within a Lambda function. The Chromeless Proxy [uses](https://github.com/graphcool/chromeless/blob/master/serverless/serverless.yml#L46) the [serverless-plugin-chrome](https://github.com/adieuadieu/serverless-chrome/tree/develop/packages/serverless-plugin) package...

@mexin Make sure you only .zip relevant dependencies. E.g. are you shipping a huge `node_modules` folder? (with devDependencies?)

Each instance of `new Chromeless` will [create it's own tab](https://github.com/graphcool/chromeless/blob/master/src/chrome/local.ts#L44) and then [close it](https://github.com/graphcool/chromeless/blob/master/src/chrome/local.ts#L100) when you call `chromeless.end()`. When passing the `remote: true` option, each instance will connect to it's...

@sul4bh make sure each instance has it's own debugger port with `--remote-debugging-port=XXXX` Typically Chrome doesn't like to run more than one instance of itself. To run multiple, separate instances of...

@sul4bh Hm.. Internally, `chrome-launcher` will already try to spawn Chrome on a random port, so perhaps the change to Chromeless would be that, if no port is specified, we _don't_...

Do we still need to pin to `[email protected]` or does the latest version of `serverless-plugin-chrome` resolve the `Error: Unknown command: protocol` issue?

@aml11 thanks for bringing this up. We're aware of the EventEmitter memory leak and have a fix coming for it soon.