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 🙏

© 2026 – Pkg Stats / Ryan Hefner

hyperdht-inspector

v0.1.1

Published

Inspector protocol over HyperDHT for Bare and Node.js

Readme

hyperdht-inspector

Use the inspector protocol over HyperDHT with Bare or Node.js

[!WARNING] This package is a work in progress and is still at a very early stage of development. Its API and behavior can change without notice. Do not use it in production until a stable release is available.

For the client CLI, see hyperdht-inspector-cli

Install

npm install hyperdht-inspector

Use

Create the server in the process that you want to inspect:

const HyperDHT = require('hyperdht')
const ProtomuxRpcRouter = require('protomux-rpc-router')
const { Server } = require('hyperdht-inspector')

const dht = new HyperDHT()
const router = new ProtomuxRpcRouter()
const inspector = new Server(router)
const server = dht.createServer((stream) => inspector.handleConnection(stream))

await Promise.all([router.ready(), server.listen()])
console.log(server.publicKey)

For production use, add router middleware before you create Server. Use it to authenticate the client peer key:

const allowedClientKeys = [trustedClientPublicKey]

router.use({
  async onrequest({ connection }, next) {
    const allowed = allowedClientKeys.some((key) => key.equals(connection.remotePublicKey))
    if (!allowed) throw new Error('Unauthorized inspector client')

    return next()
  }
})

Connect a client and send Chrome DevTools Protocol requests:

const HyperDHT = require('hyperdht')
const { Client } = require('hyperdht-inspector')

const dht = new HyperDHT()
const client = new Client(dht, serverPublicKey)

client.on('HeapProfiler.addHeapSnapshotChunk', ({ params }) => {
  console.log(params.chunk)
})

await client.post('HeapProfiler.takeHeapSnapshot')
await client.close()
await dht.destroy()

By default, the server allows these methods:

  • HeapProfiler.takeHeapSnapshot
  • Profiler.enable
  • Profiler.start
  • Profiler.stop

By default, the server sends only the HeapProfiler.addHeapSnapshotChunk event. The CPU profile is returned by Profiler.stop.

Requests intentionally omit params. To allow more methods or events, set allowMethods and allowEvents:

const inspector = new Server(router, {
  allowMethods: ['Runtime.enable', 'Runtime.getIsolateId'],
  allowEvents: ['Runtime.consoleAPICalled']
})

The application owns the DHT nodes, router, server, and access control. Allow only trusted client keys. Close all resources during shutdown.

Test

RPC requests use the Hyperschema encoding defined in build.js. Regenerate spec/hyperschema after changing the schema:

npm run build

Responses and notifications use JSON. The binary request encoding requires both client and server to be updated together from the previous JSON request format.

npm test
npm run test:bare

License

Apache-2.0