Hacker GitHub

← All repos

cyrus-and/chrome-remote-interface

View on GitHub ↗ ★ 4,558 JavaScript

Chrome Debugging Protocol interface for Node.js

9 mentions on Hacker News by 7 people: 2 stories, 7 comments · first 2013-07-10 · latest 2020-04-28

Mentions per year 9 mentions · busiest year 2017 (4)
20082026
  1. …, etc >:) Virtual context creation+release could indeed be the problem. FWIW https://github.com/cyrus-and/chrome-remote-interface makes using Chrome's remote debug protocol (to open and close tabs) utterly trivial; or you could just ru
    comment by exikyut · 2020-04-28 · in X410 – X Server for Windows 10
  2. …up with puppeteer's api changes. Plus, the abstraction leaked. Taiko is now built on the excellent https://github.com/cyrus-and/chrome-remote-interface
  3. Works for me when using https://github.com/cyrus-and/chrome-remote-interface
  4. Also checkout https://github.com/cyrus-and/chrome-remote-interface for an easy way to fully control those headless instances
  5. Yes: https://github.com/cyrus-and/chrome-remote-interface/wiki/Tr... But ultimately selenium and webdriver.io will do a better job at this
  6. …cookies, console messages, DOM tree, etc). For Chrome, this is probably the best library available: https://github.com/cyrus-and/chrome-remote-interface . Headless is working as well, but still has some issues.
  7. ▲ 38
    Show HN: Chrome Remote Debugging Protocol interface
    story by cyrusand · 2016-08-28 · 7 comments
  8. It does expose a websocket other apps can use to control Chrome (such as this node module: https://github.com/cyrus-and/chrome-remote-interface or the Chrome webdriver )
    comment by wildpeaks · 2014-12-29 · in Chrome DevTools outside of the browser
  9. ▲ 1
    Chrome remote interface
    story by wslh · 2013-07-10 · 0 comments