Puppeteer: Headless Chrome Node API

Re:Puppeteer: Headless Chrome Node API by equasar on Wednesday August 16, 2017 @05:27PM (#15031528)

How can this work on Cloud Functions/Amazon Lambda/Azure Functions without installing the dependencies each time it has to run?

Haven't done anything before with those serverless approaches.

[ Parent | on HN ]

Re:Puppeteer: Headless Chrome Node API by peterbaumgarten on Wednesday August 16, 2017 @10:30PM (#15033314)

It probably will not run on AWS Lambda as the version of Node required by Puppeteer is too recent.

From puppeteer readme[1]

> Puppeteer requires Node version 7.10 or greater

From AWS website[2]

> AWS Lambda supports the following runtime versions:

> Node.js – v4.3.2 and 6.10.3

[1] https://github.com/GoogleChrome/puppeteer/blob/master/README...

[2] http://docs.aws.amazon.com/lambda/latest/dg/current-supporte...

[ Parent | on HN ]

Re:Puppeteer: Headless Chrome Node API by equasar on Thursday August 17, 2017 @12:20AM (#15033790)

sight... I checked Azure Functions and Cloud Functions and they are running 6.x versions of node as well.

[ Parent | on HN ]

Re:Puppeteer: Headless Chrome Node API by applejuice0 on Thursday August 17, 2017 @02:54AM (#15034347)

AWS Lambda presents a base image ready to be provisioned as multiple instances.

If you are familiar with Docker you can think about Lambda image as a small Docker image, while real work will be done in instances (Docker containers) created from this image.

Usual scenario is to provide ready to go image (with all source code, npm packages being installed, with Chrome Headless plugin, etc). Then AWS/Azure will run VM instances based on the image for almost every function request. Most of the time spinning such lite VMs takes no more than a couple of seconds.

[ Parent | on HN ]