TracerBench / chrome-debugging-client

An async / await friendly debugging client for chrome

TracerBench/chrome-debugging-client Issues

Allow passthrough of `ws` options to websocket factory
Updated a year ago1
forkWithWebSocket
Updated 2 years ago1
printToPDF generating different and unexpected content with chrome print
Closed 3 years ago1
Use in deno
Closed 3 years ago4
`await chrome.close()` hangs
Closed 3 years ago1
set working directory for node
Closed 4 years ago3
Potential buffering issue
Closed 4 years ago
Proposal: Add `spawnOrInstallChrome` method
Updated 5 years ago1
ChromeDebuggerClient currently fails on my mac
Closed 5 years ago1
ChromeDebuggerClient currently fails on my mac
Closed 5 years ago
Running this library from browser
Closed 5 years ago3
Generate interfaces for domain classes
Closed 5 years ago3
Intermittent "failed waiting for port file"
Closed 6 years ago1
Make --no-proxy-server configurable
Closed 6 years ago6
RFC In light of puppeteer overlapping this library, does it make sense to maintain?
Closed 6 years ago6
Using chrome-debugging-client as a git dependency does not build the library
Closed 7 years ago
There is no session.spawn(...) method
Closed 7 years ago1
How to use with Ubuntu and Chromium
Closed 7 years ago1
Resuming node execution
Closed 7 years ago14
spawning canary presumes installed at /Applications but I have it in ~/Applications (macOS)
Closed 7 years ago2
Web socket to chrome not opened
Closed 7 years ago2
Allow spawning browser at custom window sizes.
Closed 8 years ago1