A reverse proxy for Chrome DevTools Protocol that captures, coalesces, and logs commands and events for debugging.
chrome-protocol-proxy is a reverse proxy tool designed for debugging applications that use Chrome's DevTools Protocol. It captures, logs, and structures all commands and events between a client and Chrome, making it easier to inspect and troubleshoot protocol interactions. The tool is a fork of chromedp-proxy and adds features like colored output, request-response coalescing, and session support.
Developers and QA engineers who work with Chrome's DevTools Protocol, such as those building automation scripts, debugging tools, or headless browser applications.
Developers choose chrome-protocol-proxy for its intelligent logging capabilities, which simplify debugging by providing clear, structured insights into protocol communication without requiring deep knowledge of the protocol's raw format.
Chrome DevTools Protocol Proxy - intelligent proxy for debugging purposes
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides color-coded logs for protocol frames, making it easy to read and distinguish between commands and events at a glance, as highlighted in the README's features.
Matches requests with their responses, simplifying debugging by grouping related data, which is a core feature mentioned in the README.
Handles flatted sessions and splits logs by connection and session IDs, crucial for debugging multi-target scenarios, as detailed in the features list.
Calculates and displays time differences between consecutive frames to help identify performance issues, a feature explicitly noted in the README.
It only works with Chrome's DevTools Protocol, making it useless for debugging other browsers or protocols, limiting its versatility in cross-browser testing.
Lacks a graphical user interface, relying solely on terminal output, which can be less intuitive for developers accustomed to visual debuggers.
Adds an extra layer to the debugging setup, which can introduce latency and require additional configuration, as seen with the need to specify listen and remote addresses via flags.