TracerBench/chrome-debugging-client

Issues

• Allow passthrough of `ws` options to websocket factory

  #218 opened 2 years ago by prescience-data
  1

• forkWithWebSocket

  #211 opened 3 years ago by samdoeswork
  1

• printToPDF generating different and unexpected content with chrome print

  #57 opened 3 years ago by rawbin-
  1

• Use in deno

  #59 opened 3 years ago by Dialga
  4

• `await chrome.close()` hangs

  #190 opened 3 years ago
  1

• set working directory for node

  #58 opened 4 years ago by Xenorage
  3

• Potential buffering issue

  #107 opened 4 years ago by chadhietala
  0

• Proposal: Add `spawnOrInstallChrome` method

  #48 opened 5 years ago by rwjblue
  1

• ChromeDebuggerClient currently fails on my mac

  #41 opened 5 years ago by stefanpenner
  1

• ChromeDebuggerClient currently fails on my mac

  #42 opened 5 years ago by stefanpenner
  0

• Running this library from browser

  #33 opened 5 years ago by oldrich-s
  3

• Generate interfaces for domain classes

  #27 opened 5 years ago by asakusuma
  3

• Intermittent "failed waiting for port file"

  #26 opened 6 years ago by asakusuma
  1

• Make --no-proxy-server configurable

  #10 opened 6 years ago by jvilk
  6

• RFC In light of puppeteer overlapping this library, does it make sense to maintain?

  #14 opened 6 years ago by krisselden
  6

• Using chrome-debugging-client as a git dependency does not build the library

  #12 opened 7 years ago by EliSnow
  0

• There is no session.spawn(...) method

  #15 opened 7 years ago by bsurai
  1

• How to use with Ubuntu and Chromium

  #16 opened 7 years ago by bsurai
  1

• Resuming node execution

  #5 opened 7 years ago by tostercx
  14

• spawning canary presumes installed at /Applications but I have it in ~/Applications (macOS)

  #7 opened 7 years ago
  2

• Web socket to chrome not opened

  #9 opened 7 years ago by bmikkelsen22
  2

• Allow spawning browser at custom window sizes.

  #2 opened 8 years ago by rwjblue
  1