Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

chrome-debugging-client

Package Overview
Dependencies
Maintainers
2
Versions
39
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

chrome-debugging-client

An async/await friendly Chrome debugging client with TypeScript support

  • 1.0.0-beta.2
  • npm
  • Socket score

Version published
Maintainers
2
Created
Source

chrome-debugging-client

Build Status npm install size

An async/await friendly Chrome debugging client with TypeScript support, designed with automation in mind.

Features

  • Promise API for async/await (most debugger commands are meant to be sequential).
  • TypeScript support and uses "devtools-protocol" types, allowing you to pick a protocol version.
  • Launches Chrome with a new temp user data folder so Chrome launches an isolated instance. (regardless if you already have Chrome open).
  • Opens Chrome with a pipe message transport to the browser connection and supports attaching flattened session connections to targets.
  • Supports cancellation in a way that avoids unhandled rejections, and allows you to add combine additional cancellation concerns.
  • Supports seeing protocol debug messages with DEBUG=chrome-debugging-client
  • Use with race-cancellation library to add timeouts or other cancellation concerns to tasks using the connection.
  • The library was designed to be careful about not floating promises (promises are chained immediately after being created, combining concurrent promises with all or race), this avoids unhandled rejections.

Examples

Spawn Chrome And Take Heap Snapshot

const { spawnChrome } = require("chrome-debugging-client");
const { writeFileSync } = require("fs");

main();

async function main() {
  const chrome = spawnChrome();
  try {
    const browser = chrome.connection;

    browser.on("error", err => {
      // underlying connection error or error dispatching events.
      console.error(`connection error ${err.stack}`);
    });

    const { targetId } = await browser.send("Target.createTarget", {
      url: "about:blank",
    });

    await browser.send("Target.activateTarget", { targetId });

    const page = await browser.attachToTarget(targetId);

    let buffer = "";
    await page.send("HeapProfiler.enable");
    page.on("HeapProfiler.addHeapSnapshotChunk", params => {
      buffer += params.chunk;
    });

    await page.send("HeapProfiler.takeHeapSnapshot", {
      reportProgress: false,
    });

    writeFileSync("heapsnapshot.json", buffer);

    await browser.send("Target.closeTarget", { targetId });

    // graceful browser shutdown
    await chrome.close();
  } finally {
    await chrome.dispose();
  }
}

Debugging Node

const { spawnWithWebSocket } = require("chrome-debugging-client");

main();

async function main() {
  // start node requesting it break on start at debug port that
  // is available
  const node = await spawnWithWebSocket(process.execPath, [
    "--inspect-brk=0",
    "-e",
    `const obj = {
      hello: "world",
    };
    debugger;
    console.log("end");`,
  ]);
  const { connection } = node;
  try {
    // we requested Node to break on start, so we runIfWaitingForDebugger
    // and wait for it to break at the start of our script
    await Promise.all([
      connection.until("Debugger.paused"),
      connection.send("Debugger.enable"),
      connection.send("Runtime.enable"),
      connection.send("Runtime.runIfWaitingForDebugger"),
    ]);
    // right now we are paused at the start of the script

    // resume until debugger statement hit
    const [debuggerStatement] = await Promise.all([
      connection.until("Debugger.paused"),
      connection.send("Debugger.resume"),
    ]);

    // get the call frame of the debugger statement
    const [callFrame] = debuggerStatement.callFrames;
    const { callFrameId } = callFrame;

    // eval obj at the debugger call frame
    const { result } = await connection.send(
      "Debugger.evaluateOnCallFrame",
      {
        callFrameId,
        expression: "obj",
        returnByValue: true,
      },
    );

    console.log(result.value); //= { hello: "world" }

    // resume and wait for execution to be done
    await Promise.all([
      connection.until("Runtime.executionContextDestroyed"),
      connection.send("Debugger.resume"),
    ]);

    // Node is still alive here and waiting for the debugger to disconnect
    // when we close the websocket after resuming
    // Node should exit on its own
    node.close();

    await node.waitForExit();
  } finally {
    await node.dispose();
  }
}

FAQs

Package last updated on 21 Jun 2019

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc