Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

We're fans of LucianoGanga's project (and of Chromeless, Doffy, Chrominator, Chromy, Navalia). I can tell you from personal experience that dealing with the raw DevTools Protocol isn't ideal for a developer writing an automation script, so it's clear there's demand for libraries with this higher-level API.

Would love to know if there's a feature parity concern you have or what you'd like to see from puppeteer (or any of these projects). (My personal feature unicorn: generate not a static screenshot but a proper video of a page session)



Hi @paulirish! I started with your unicorn haha, I wrote only a few lines of code, to use the screencast events to save the frames of a page. Here's the branch with that: https://github.com/LucianoGanga/simple-headless-chrome/tree/...

And here is the thread I'm gonna use to discuss this: https://github.com/LucianoGanga/simple-headless-chrome/issue...

If someone has an idea of what the "ideal implementation" would look like, I'd really appreciate it!


Chromeless allows for the setting of cookies. I noticed in an issue for Puppeteer that it wasn't seen as a high priority. Our use-case (session based cookies) rely on a cookie being set in order for our PDF screenshots to work.

Any chance you could give us some insight on when this may be available?


One of the puppeteer devs tells me he started on cookies last night. You'll see a PR soon. :)


Awesome! So stoked on this. After some Phantom headaches we're really excited to transition to Chrome Headless.


We're mainly using these things for screenshots of existing corporate intranet tools that are then surfaced to slack. Headless chrome is finally giving us screenshots that are actually authentically what you would actually see on the screen. PhantomJS came close but still has issues.


Your unicorn would be lovely though :D




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: