81–90 of 92 posts
So to clarify - this is basically a Node.JS wrapper around Chrome headless, right? =_) Seems pretty awesome. My use case is to take screenshots of various pages - the docs don't mention the default viewport dimensions, btw.
agreed no default is mentioned but you can declare with `await chromeless.viewport(1024, 800)`
https://chromeless.netlify.com/#src=const%20chromeless%20=%2...
I'll just add some related projects I've used / tried in the past. The promise of fast execution time in parallel is tempting with Chromeless. Thanks for sharing. - https://github.com/webdriverio/webdriverio - https://github.com/nightwatchjs/nightwatch - https://github.com/assaf/zombie - https://github.com/dhamaniasad/HeadlessBrowsers
Thanks a lot for bringing this up. We've tried all of the projects listed above before we began to implement Chromeless. Ultimately it was the combination of using headless Chrome and the ability to execute code in parallel on Lambda, which made us invest in Chromeless.
You can then use the vm/container as a function to match AWS lambda.
Is it the that the api is more-user friendly or selenium w3c complaint?
Genuinely curious, don't know much about this project.
Wish it had a python wrapper.
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/ Let me know if you have any questions :)
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.
shamless plug: i've also written a high level api on top of the chrome remote debugger chrominator [1] similar idea. chrominator use promises instead of a fluent api. it also follows the selenium w3c spec where possible. it does cool stuff with evaluate and evaluateAsync where it resolves the remote object to something usable. to be fair there are a few other projects i know about that wrap chrome remote debugger wit…
https://medium.com/@kensoh/chromeless-chrominator-chromy-nav...
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/ Let me know if you have any questions :)
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.
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-...
Earlier quoted context omitted.
Also interested, this would be excellent fit for a use case I have archiving certain important government websites. Btw, does the .viewport() option not work in the demo? I'm seeing a `TypeError: Failed to fetch` when I set one.
You need to do it like this: https://chromeless.netlify.com/#src=const%20chromeless%20=%2...
This is a really cool project, but looking closer at the API and issues raised it seems that the features are being over-promised. - "Do pretty much everything you've used PhantomJS, NightmareJS or Selenium for before". The main features of those tools plus their ability to handle a large range of edge cases are built up over the years in production use and do not seem to be already in Chromeless. Also, Lambda costs…
Hi kensoh, thanks a lot for your great comment. I totally agree with you! It took years for these tools to mature and so it will be the case for Chromeless. There are probably a range of edge-cases that yet have to be solved but like you said, I'm very optimistic that together with our great community, we'll be able to handle all of these cases. The big incentive for us to create Chromeless instead of using Nightmare…
Yes perfectly, I believe for any one very serious about test automation or browser automation in general, they will make their own tool and bring it to market if there isn't already one that meets their needs. :)