A client-side JavaScript CDP agent that enables remote debugging of webpages using Chrome DevTools.
Devtools Remote Debugger is a client-side JavaScript implementation of the Chrome DevTools Protocol (CDP) that enables remote debugging of webpages. It allows developers to use Chrome DevTools to inspect, debug, and interact with a webpage by loading a small JavaScript snippet, with communication routed through a Node.js WebSocket layer.
Web developers and QA engineers who need to debug webpages in environments where direct browser DevTools access is limited, such as embedded webviews, kiosks, or remote devices.
It provides a seamless, familiar debugging experience using Chrome DevTools without requiring browser extensions or complex configurations, making it ideal for debugging webpages in constrained or remote scenarios.
Use devtools against a webpage; a CDP agent implemeted in client-side JS
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Implements the Chrome DevTools Protocol, allowing developers to use the exact same debugging interface they are accustomed to for local development, as highlighted in the README's philosophy.
Includes all major panels like Elements, Console, Sources, Network, and Application, with live previews demonstrated in the README's GIFs, enabling full inspection and debugging capabilities.
Requires only loading a single JavaScript file (cdp.js) on the target webpage, simplifying the process of enabling remote debugging without browser extensions.
Addresses same-origin policy issues by recommending crossorigin attributes for external resources, as noted in the Additional Information section, making it suitable for debugging complex pages.
Requires configuring environment variables, building the project, and running a Node.js server, as outlined in the 'How to use?' section, which adds significant overhead compared to native DevTools.
Lacks DevTools features like Performance or Memory profiling, limiting its use for performance debugging beyond basic inspection and network monitoring.
Injecting external JavaScript and using WebSocket communication can introduce security vulnerabilities and potential latency, especially in production or sensitive environments.