chrome-aws-lambda icon indicating copy to clipboard operation
chrome-aws-lambda copied to clipboard

Chromium Binary for AWS Lambda and Google Cloud Functions

Results 77 chrome-aws-lambda issues
Sort by recently updated
recently updated
newest added

## What would you like to have implemented? Upgrade for Puppeteer 13.1 along with necessary Chrome binaries ## Why would it be useful? There are quite some great extra features...

enhancement

Hi, thanks for putting this package together, it looks great! I'm just wondering if there are security implications that are introduced be setting some of the flags that are needed...

Apologies for what seems like a straightforward question. I cannot seem to find anyone doing this successfully. Is it possible to create a .NET Core lambda function in AWS that...

I am trying to run a lambda with a custom image (based on `public.ecr.aws/lambda/nodejs:14`) I've placed `fonts/NotoColorEmoji.ttf` in my folder yet I still cannot render emojis correctly. Here's my code:...

## What would you like to have implemented? Support an environment variable (such as `CHROME_AWS_LAMBDA_ASSUME_HEADLESS`) to optionally short circuit the `serverless` variable checks in `Chromium.headless`. For example, this could look...

enhancement

* `chrome-aws-lambda` 10.1.0: * `puppeteer` / `puppeteer-core` 13.6.0: * OS: Linux * Node.js Version: 14 ## Expected Behavior No error happening ## Current Behavior This error: { "errorType": "Runtime.UserCodeSyntaxError", "errorMessage":...

bug

Im using `chrome-aws-lambda` and `playwright-core` just like the example. At the moment of usage of it in a serverless functions, i get the error `"Error: ENOENT: no such file or...

Make AWS Lambda Nodejs regex more tolerant to support custom runtimes, fixes #268 we're happy to prefix our exection env var with `AWS_Lambda_nodejs`, although I guess another option would be...

## What would you like to have implemented? Running Node 16 in a Custom Runtime on Lambda, requires this workarond: ```js process.env.AWS_EXECUTION_ENV = 'AWS_Lambda_nodejs14.x' const { default: chromium } =...

enhancement

## Environment * `chrome-aws-lambda` Version: `5.5.0` * `puppeteer` / `puppeteer-core` Version: `5.5.0` * OS: `Mac` * Node.js Version: `v12.18.3` * Lambda / GCF Runtime: `nodejs12.x` ## Expected Behavior This code...

bug