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

bsdash

v1.0.1

Published

go-ipfs bitswap dashboard

Downloads

9

Readme

bsdash - dashboard for go-ipfs bitswap

This is a simple dashboard for bitswap in go-ipfs. It consumes the API's /logs route.

bsdash in the terminal

Install it:

npm install -g bsdash

Run it:

# daemon should be running in the background
ipfs daemon &

# run bsdash
bsdash

You'll see something like this:

Note: open term window > 110 chars, or it will not draw properly.

(bug in clivas: see https://github.com/mafintosh/clivas/issues/2)

*** IPFS Bitswap Dash ***
Active Requests 0:
Provide Workers 4:
    worker 0: QmPtszRZEY9XDMss33v8rvyn29xVtPo2aLfJFUEjevrbfV
    worker 1: QmZ2mXY7RjgnAX3hMqyRPU6D3bc2NgcHBeo6jojy7Zby4k
    worker 2: QmQm3NTmeXZsojn3uG53Tqw5a8kjUWbwYk8R5C6q4SnBj9
    worker 3: QmcEUEwMNt4nfzxnz4CsJ6a2FtuVySj4RG6LNFp8GBChVt
Task Workers 8:
    worker 0: QmcH58rDCsmaLATkGbLB1KM1JEU9xmeB5D7gQzaMbRFUqH to QmSyjxWfaAmnaK3yBVZWUsfcPV4AFXEfJURuqLvHMxj3Lk
    worker 1: idle
    worker 2: QmUzFhUTN8odFZcMqmL3fRybgDvLzcrQL4CZt5EqS9Vex2 to QmSyjxWfaAmnaK3yBVZWUsfcPV4AFXEfJURuqLvHMxj3Lk
    worker 3: QmbiAJspmFbSTvPDjFE7BLfiDmqDizDmt3sjPoJk8fhhng to QmSyjxWfaAmnaK3yBVZWUsfcPV4AFXEfJURuqLvHMxj3Lk
    worker 4: QmdqYvoGKJQUA8MNCgqksWwKq17w1s8MBXGnNhiSnwAU8k to QmSyjxWfaAmnaK3yBVZWUsfcPV4AFXEfJURuqLvHMxj3Lk
    worker 5: QmeEow8iK8LmyXV4HXeznPouWrk6374oeGnXJcPqWHK7Pe to QmSyjxWfaAmnaK3yBVZWUsfcPV4AFXEfJURuqLvHMxj3Lk
    worker 6: QmQkYAkMo5GU4hNdAghBwwYdRfwVGHfcma129PB5XNPhqF to QmSyjxWfaAmnaK3yBVZWUsfcPV4AFXEfJURuqLvHMxj3Lk
    worker 7: QmRNLf435E3QRwundUUhKe1TUoRBHiZPoQZKdpVAYLYekv to QmSyjxWfaAmnaK3yBVZWUsfcPV4AFXEfJURuqLvHMxj3Lk
Rebroadcast Worker: idle
Provider Connector:

events: 1339/47203 prints: 3946 (25ms delay)

Usage

usage: bsdash [OPTIONS]

Options:
  -h, --help       this help text
  -s, --state      show only the state
  -l, --ratelimit  rate limit draw (ms)  [default: 25]
  -a, --api-url    api url               [default: "http://localhost:5001"]

--api-url - change the api location

If your IPFS API is elsewhere, run: http://localhost:5001

bsdash lib module

If you want to make your own dashboard, use the the module to get the bitswap dashboard state from the api event logs.

var bsdash = require('./index')
var api = "http://localhost:5001"
bsdash(api, function(err, state) {
  if (err) throw err

  console.log(state)
})