Refactor into an npm package, serverless-plugin, and provide example handlers as individual Serverless functions

It seems to make a lot of sense to turn serverless-chrome into an npm package, and separate Serverless plugin.

The plugin would hook into the Serverless after:createDeploymentArtifacts life cycle event and wrap around the handler function. The wrapper would then make sure that headless Chrome is running before calling the wrapped handler function.

https://serverless.com/framework/docs/providers/aws/guide/plugins/

1. update for nodejs v6.10 (and remove Buffer.from hack/polyfill)
2. refactor chrome bundle and chrome spawning into an npm package (npm: lambda-chrome ?)
3. Serverless plugin, using npm package
4. use Rollup(docs) for npm packages
5. remove serverless-webpack plugin dependency
6. create Serverless functions for each example handler
7. ~change postinstall script to create serverless.yml instead of config.js from one of the example serverless.yml files~
8. update all the documentation

[jgollub1]

Hi, thanks for all the work you’ve done! I was wondering if anyone could direct me to a web-scraping example (eg just rendering the DOM and returning it) of serverless-chrome that is deployable to aws lambda? I’ve been tinkering around with your package for a little while but haven’t had much luck

[chriszarate]

@adieuadieu That’s it! ClaudiaJS, by default, uploads the payload directly. However, it provides an option to upload via S3. Testing again, I was able to upload a larger payload:

claudia create --use-s3-bucket my-bucket --handler index.handler

Since your npm package includes the uncompressed binary, Claudia will in effect require the use of the --use-s3-bucket to successfully upload. That’s a small price to pay for the resulting increase in spin-up speed, however.

I’ll put together a PR with a Claudia example.