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

tapenet

v1.4.0

Published

Test runner for distributed systems based on mininet and tape

Readme

tapenet

Test runner for distributed systems based on mininet and tape

npm install tapenet

Usage

var test = require('tapenet')

var h1 = test.createHost()
var h2 = test.createHost()
var s1 = test.createSwitch()

h1.link(s1)
h2.link(s1)

test('start a server and connect to it', function (t) {
  t.run(h1, function () {
    // this is run inside a mininet container on h1
    var net = require('net')

    h2.on('listening', function (ip) {
      var socket = net.connect(10000, ip)
      var bufs = []

      socket.on('data', data => bufs.push(data))
      socket.on('end', function () {
        t.same(Buffer.concat(bufs).toString(), 'hello from h2')
        t.end()
      })
    })
  })

  t.run(h2, function () {
    // this is run inside a mininet container on h2
    var net = require('net')

    var server = net.createServer(function (socket) {
      t.pass('got connection')
      socket.write('hello from h2')
      socket.end()
    })

    server.listen(10000, function () {
      h2.emit('listening', global.ip)
    })
  })
})

CLI test runner

Similar to tape, you can either run a test by simply running a test file with node or you can use the cli runner

npm install -g tapenet
tapenet *.net.js

API

var h = test.createHost()

Same as mininet.createHost()

var s = test.createSwitch()

Same as mininet.createSwitch()

test.mininet

The underlying mininet instance.

test(name, runner)

Start a test. name is a description of your test and runner should be a function. When the test is run, runner is ran with the argument t which is a tape test instance.

t.run(host, source)

In addition to all the other tape test methods, t.run will run a source function inside a mininet host. The host will have access to the test object through the t variable, and a set of shared event emitters h1, h2, ... If you emit an event on any of those event emitters it will be emitted across all mininet hosts currently running.

Topologies

tapenet comes bundles with some useful topologies.

// same as h1.link(s1), h2.link(s1)
var {h1, h2} = test.topologies.basic()

For more see topologies/

License

MIT