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

v8-debug

v1.0.1

Published

v8 debugger extending API

Downloads

9,718

Readme

Build Status Build status npm version

v8-debug

Provides extending API for node internal debugger protocol (based on v8 debugger protocol)

This is a part of node-inspector.

Installation

npm install v8-debug

API

registerCommand(name, callback)

Registers new debug processor command, like lookup.

callback accepts two arguments - request and response.

You need to modify response.body if you want to return something to caller.

debug.registerCommand('_lookup', function(request, response) {
  var test = request.attributes;
  //do someting here
  //and modify response
  response.body = {
    test: test
  };
});

registerEvent(eventName)

This is a shortcut for:

debug.registerCommand('someEvent', debug.commandToEvent);

execCommand(commandName, attributes)

Calls debug processor command like 'lookup'.

attributes will be passed to registerCommand.callback as request.attributes.

attributes needs to be valid JSON object.

debug.registerCommand('_lookup', function(request, response) {
  var test = request.attributes;
  //do someting here
  //and modify response
  response.body = {
    test: test
  };
});

debug.execCommand('_lookup', { attr: 'test' });

emitEvent(eventName, attributes)

This is a semantic alias for execCommand

debug.emitEvent('myEvent', { attr: 'test' });

commandToEvent(request, response)

response object has a different structure for commands and events.

By default registerCommand.callback receives command's response.

This is a small converter.

debug.registerCommand('someEvent1', function(request, response) {
  debug.commandToEvent(request, response);
});

debug.registerCommand('someEvent2', debug.commandToEvent);

Use debug.registerEvent instead of this.

runInDebugContext(script)

(alias get)

Evaluates string or function (will be stringifyed) in debug context.

var MakeMirror = debug.get('MakeMirror');
var mirror = MakeMirror({ test: 1 });

getFromFrame(index, value)

Tries to receive a value from targeted frame scopes

function a(options) {
  //...
  b();
}

function b() {
  // There is no info about `options` object
  var options = debug.getFromFrame(1, 'options');
}

enableWebkitProtocol()

Enables experimental usage of WebKit protocol

registerAgentCommand(command, parameters, callback)

Experimental method for registering WebKit protocol handlers

Usage

Simple console.log checking

var debug = require('v8-debug');

debug.registerEvent('console.log');

console.log = (function(fn) {
  return function() {
    debug.emitEvent('console.log', {message: arguments[0]} /*, userdata*/);
    return fn.apply(console, arguments);
  }
} (console.log));

For more experience see protocol documentation