3 ms·

I'm really excited to finally open-source Chromeless. We've used NightmareJS and similar tools before to run integration tests but these basically added ~20min

I'm really excited to finally open-source Chromeless. We've used NightmareJS and similar tools before to run integration tests but these basically added ~20min to each build. With Chromeless we were able to reduce this time to under a minute! Here is btw a demo playground to try it out: https://chromeless.netlify.com/ https://chromeless.netlify.com/ Let me know if you have any questions :)

ivan_ah 9y ago
How difficult would it be to also support google cloud functions and the azure offerings? This seems like a really useful standard tool that lots of people might want to use. CI jobs on pull requests that take seconds instead of minutes = big win!
- jpalomaki 9y ago
  Azure Container Instances might be good for this: https://azure.microsoft.com/en-us/blog/announcing-azure-container-instances/ https://azure.microsoft.com/en-us/blog/announcing-azure-cont...
- nodesocket 9y ago
  +1 for Google Cloud Functions.
- schickling 9y ago
  This should actually be pretty easy. There is no reason that this is bound to AWS Lambda. We're more than open to accept PRs that enable multi-cloud support.
djhworld 9y ago
How did you manage to get Chrome headless compiled and running on AWS? I spent a while looking at this a few months ago to do a similar project (run chrome in headless mode on AWS Lambda) but couldn't get the binary to work.
- adieuadieu 9y ago
  We're using serverless-chrome for the headless-chrome-on-aws-lambda part. https://github.com/adieuadieu/serverless-chrome https://github.com/adieuadieu/serverless-chrome If you're interested in how serverless-chrome works, I wrote an article on how to get headless chrome running on AWS Lambda from scratch here: https://medium.com/@marco.luethy/running-headless-chrome-on-aws-lambda-fa82ad33a9eb https://medium.com/@marco.luethy/running-headless-chrome-on-...

3 ms·

I'm really excited to finally open-source Chromeless. We've used NightmareJS and similar tools before to run integration tests but these basically added ~20min

by schickling 9y ago

ivan_ah 9y ago
How difficult would it be to also support google cloud functions and the azure offerings? This seems like a really useful standard tool that lots of people might want to use. CI jobs on pull requests that take seconds instead of minutes = big win!
- jpalomaki 9y ago
  Azure Container Instances might be good for this: https://azure.microsoft.com/en-us/blog/announcing-azure-container-instances/ https://azure.microsoft.com/en-us/blog/announcing-azure-cont...
- nodesocket 9y ago
  +1 for Google Cloud Functions.
- schickling 9y ago
  This should actually be pretty easy. There is no reason that this is bound to AWS Lambda. We're more than open to accept PRs that enable multi-cloud support.
djhworld 9y ago
How did you manage to get Chrome headless compiled and running on AWS? I spent a while looking at this a few months ago to do a similar project (run chrome in headless mode on AWS Lambda) but couldn't get the binary to work.
- adieuadieu 9y ago
  We're using serverless-chrome for the headless-chrome-on-aws-lambda part. https://github.com/adieuadieu/serverless-chrome https://github.com/adieuadieu/serverless-chrome If you're interested in how serverless-chrome works, I wrote an article on how to get headless chrome running on AWS Lambda from scratch here: https://medium.com/@marco.luethy/running-headless-chrome-on-aws-lambda-fa82ad33a9eb https://medium.com/@marco.luethy/running-headless-chrome-on-...