Marco Lüthy

Hi @anvaka — That's interesting. When building chromium from source, it also produces a `libosmesa.so` shared library. I just don't include it as it was my understanding that WebGL wasn't...

I can try doing a build with `enable_swiftshader` if someone else can help test the resulting binary on aws lambda.

Thank you! I've started a build. If it builds successfully, I'll provide a link to the binary in the morning (UTC+2).

OK; binary is available [here](https://s3.amazonaws.com/serverless-chrome-binaries/chromium/experimental-swiftshader/headless-chromium-68.0.3440.106-amazonlinux-2017-03.zip). It's also available in a Docker image: [adieuadieu/headless-chromium-for-aws-lambda:experimental-swiftshader](https://cloud.docker.com/swarm/adieuadieu/repository/docker/adieuadieu/headless-chromium-for-aws-lambda/general)

@vsantosu ah shoot. you're right. I'll get you those library binaries, as well. Need to do another build, though. The EC2 instance I built on was terminated.

Hi @alekseykulikov, I apologise for my brief reply. In short: I don't really know. I haven't had a chance to dig into it much myself—but, like you've discovered, headless Chrome...

I've asked about `--single-process` and `--no-sandbox` [here](https://groups.google.com/a/chromium.org/d/msg/headless-dev/qqbZVZ2IwEw/qOoNb73gAwAJ).

@toddwprice oh that's great news! I hope Chrome looks for fonts in the same place. About the 50MB limit: if you deploy your Lambda function with the deployment package in...

@toddwprice Jump over `npm test`. Which folder are you working in? `packages/lambda` may be the best place to play around in. There's a pesudo-integration test for Serverless there which you...

@toddwprice Sure—would at 18:30 CEST work? Could you DM me on Twitter or Gitter (@adieuadieu), or email (on my GitHub profile) so we can settle on a tool/service/share usernames to...