npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

chromium-remote-debugging-proxy

v0.6.1

Published

A proxy that sits in between a chromium devtools frontend and the remote chromium being debugged and logs requests, responses and websocket messages that are exchanged.

Downloads

14

Readme

chromium-remote-debugging-proxy

A proxy that sits in between a chromium devtools frontend and the remote chromium being debugged and logs requests, responses and websocket messages that are exchanged.

screenshot

Usage

Start Proxy

crdp

Start Chromium with remote debugging enabled

./Chromium.app/Contents/MacOS/Chromium --remote-debugging-port=9222 --no-sandbox

Open DevTools in another Browser

Make sure it points to the Proxy Port (by default REMOTE_PORT -1).

localhost:9221

Installation

npm install chromium-remote-debugging-proxy

Proxy Usage

crdp <options> 

Proxies requests from chromium devtools frontend and the remote chromium being debugged and logs requests, responses and websocket messages that are exchanged.

OPTIONS:

  -l, --loglevel  level at which to log: silly|verbose|info|warn|error|silent -- default: info

  -r, --remote    overrides port at which remote Chromium is listening, same as --remote-debugging-port (default: 9222)
  -p, --port      overrides proxy port (default: --remote - 1) 
  -o, --outfile   if supplied all the incoming and outgoing messages are written to it as comma-delimited JSON, but requests and responses are not
                  all messages have a 'direction' attached to the message taking the view point of the DevTools frontend
                    outgoing: '=>'
                    incoming: '<='
                  in order to parse the resulting JSON remove the last ',' and surround it with [ ]
  
  -h, --help      Print this help message.


EXAMPLES:
  
  Assume Chromium is listening on remote debugging port 9222, make proxy listen on port 9221 and write JSON messages to ./messages.json 
    
    crdp --remote 9222 -outfile messages.json

Visualizer Usage

In order to better understand the messages the crdp-visualize is included. It will sort messages and thus group outgoing ones right next to the incoming message sent in response.

After generating a JSON message file via the crdp --outfile option do the following:

crdp-visualize ./path-to-file.json
open ./path-to-file.html

sample html

License

MIT