When trying to run with AWS Lambda I'm getting this error.
index.js is same as required by AWS Lambda with handler function and requiring my other file in index.js.
Here is code from that file:

// this one is same as example `get-browserless.js`
const getBrowserless = require('./get_browserless')

async function startTest() {
	try {
		const { text } = await getBrowserless();
		const url = 'https://google.com';
		const urlText = await text(url)
		console.log(urlText)
		return Promise.resolve();
	} catch (error) {
		console.log(error)
		return Promise.reject();
	}
}

const test = { startTest };
module.exports = test;

I've been using https://github.com/serverless/serverless and https://github.com/apex/up to deploy things to AWS Lambda and abstract away all the ugly manual config parts.

If you think it's useful, I could provide code examples of how to do this for a simple browserless script. Other things that are probably useful to demonstrate in a minimal way so users don't have to solve the exact same problems over and over again:

1. you need to babel-ify async code so it can run in Node v6.10 https://docs.aws.amazon.com/lambda/latest/dg/current-supported-versions.html
2. how to avoid running into the "package bigger than 250 meg" problem https://docs.aws.amazon.com/lambda/latest/dg/limits.html

This is something that https://github.com/sambaiz/puppeteer-lambda-starter-kit happens to implicitly document quite well

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

I'm debating over hosting a snapshot service on Lambda or Now.sh. I have questions regarding the use of this repository.

1. How many concurrent requests can this handle?
2. What happens when Chrome crashes?
3. What is the most solid configuration/usage you've found with the use of Chrome & Lambda?
4. Sites like "https://browserless.io" claim that it's best to create a browser each time you need a fresh instance to prevent issues, however doing that with this library takes roughly 7-11 seconds for a 540x720 screenshot... how do we speed this up?

I want to try to avoid crashes at all cost as well as have something that scales well.

sambaiz/puppeteer-lambda-starter-kit#8

I'm trying to get this package working on Lambda.

Lambda now supports Node 8.1.0 so that's made it easier for me.

https://aws.amazon.com/blogs/compute/node-js-8-10-runtime-now-available-in-aws-lambda/

So I set the runtime on my machine to Node 8.1.0, also the runtime on Lambda.

Following your instructions to the letter, I think.

npm install puppeteer browserless --save
npm install @browserless/aws-lambda-chrome --save

Create the two files, then zip up my node modules directory, the js files and package.json.

On upload, I get the error message, partly I guess because I'm trying to upload two versions of Chromium, yours and Puppeteer's.

What am I doing wrong?

Hey! Thanks for this great plugin. I'm facing an issue where puppeteer fails to launch the headless_shell binary.

Here's my code snippet (using the serverless framework):

const puppeteer = require('puppeteer')
const getChromePath = require('@browserless/aws-lambda-chrome')({
  path: '/tmp'
})

module.exports.handler = async (event, context) => {
  const browser = await puppeteer.launch({
    executablePath: await getChromePath()
  })

  const page = await browser.newPage()
  await page.goto('https://example.com')
  console.log(await page.title())

  await browser.close()
}

The error I get is:

  Error --------------------------------------------------

  Failed to launch chrome!
/tmp/headless_shell: /tmp/headless_shell: cannot execute binary file


TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

Any suggestions?

• https://github.com/MayhemYDG/iltorb

This is what i get when executing the lambda. But, this works on local machine using lambda-local package.

{
  "errorMessage": "Chromium revision is not downloaded. Run \"npm install\" or \"yarn install\"",
  "errorType": "Error",
  "stackTrace": [
    "assert (/var/task/node_modules/puppeteer/lib/helper.js:282:11)",
    "Function.launch (/var/task/node_modules/puppeteer/lib/Launcher.js:106:7)",
    "<anonymous>"
  ]
}

I am trying to build my own binary. I launched the recommended instance type, downloaded the build script then executed it. The script errors out:

Error: client not configured; see 'gclient config'

I was able to resolve that issue using advice found here https://bugs.chromium.org/p/v8/issues/detail?id=3787.

gclient config https://chromium.googlesource.com/v8/v8

However, running the build script again led to:

gn.py: Could not find checkout in any parent of the current path.
This must be run inside a checkout.

which is caused by gn gen out/Headless.

Have you been able to run the build script lately?