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

chrome-remote-debug-protocol

v1.2.20180422

Published

Auto generated crdp.d.ts typings from protocol.json files used by Chrome Remote Debugging Protocol

Downloads

311,911

Readme

Chrome Remote Debug Protocol

build status npm version

Goals

  • Auto-generate Client interface so third party tools can connect to Chrome, Node and other CRDP compliant servers
  • Auto-generate Server interface so ChromeDevTools can connect to engines other than Chrome and Node

How

This package is purely a typings typescript d.ts interface that is automatically generated.

It has scripts to download the latest protocol.json files from the Chromium repo, verify structural integrity based on protocol.d.ts and generate a crdp.d.ts typescript interface.

Travis CI runs a nightly job to check that protocol.json from google doesn't have structural breaks. Thanks to this project, a few have already been detected and fixed.

Usage

crdp.d.ts is a JsonRpc2 compliant interface. It is meant to be used with noice-json-rpc package.

Rather than callbacks, noice-json-rpc returns Promises. This means it can be used async-await style.

noice-json-rpc also provides a .api() to return an ES6 proxy which provides a clean api.Domain.function() calls.

Building

Checkout this project. Install the dependencies (see .travis.yml) and run

npm run download-protocols
npm run generate-crdp

Example

import fs from 'fs'
import Crdp from 'chrome-remote-debug-protocol'
import {Client} from 'noice-json-rpc'

// run connects to `node --inspect --debug-brk` process, and profiles the execution of a script
async function run() {
   try {
       // We want the api to be a CrdpClient
       const api:Crdp.CrdpClient = new Client(new WebSocket("ws://localhost:8080"), {logConsole: true}).api()

       // Initialize debugging
       await Promise.all([
           api.Runtime.enable(),
           api.Debugger.enable(),
           api.Profiler.enable(),
           api.Runtime.run(),
       ])

       // Wait until the script finishes
       await new Promise((resolve) => api.Runtime.onExecutionContextDestroyed(resolve))

       // Get the cpuProfile back
       const cpuProfile = await api.Profiler.stop()

       // Save it to a file
       fs.writeFileSync("profile.cpuProfile", JSON.stringify(cpuProfile), 'utf-8')


   } catch (e) {
       console.error(e)
   }
}
run()