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 🙏

© 2025 – Pkg Stats / Ryan Hefner

discovery-swarm-stream

v2.1.1

Published

Proxy discovery over a stream

Downloads

86

Readme

Discovery Swarm Stream

Alows clients to use discovery-channel to discover and connect to peers.

Clients connect to the server, search for "discovery keys", and the proxy automatically discovers and connects to peers and then proxies those connections to the client.

If two clients are discovering the same key, the proxy can connect them to each other if you set the connectExistingClients on the server.

By default it supports connections for the hypercore-protocol used in Dat. If you'd like to support a different protocol, provide a stream argument that conforms to what's expected in discovery-swarm.

Requires:

  • ES6 classes
  • Arrow functions
  • Weak Sets (server only)

Example

// On a server
const DSS = require('discovery-swarm-stream/server')

const swarm = new DSS({
	// Hash topics through sha1 before passing them through
	defaultHash: false,

	// Use the default discovery-swarm handshaking
	defaultHandshake: false,

	// swarm options here
	// Doesn't support UTP for now
})

const httpServer = require('http').createServer()
httpServer.listen(4200)

const server = require('websocket-stream').createServer({server: httpServer}, (ws) => {
	swarm.handleConnection(ws)
})

// On a client
const DSS = require('discovery-swarm-stream/client')
const websocket = require('websocket-stream')

const socket = websocket('ws://localhost:4200')

const swarm = new DSS({
	connection: socket,
	stream: (connection) => connection.write('hello!')
})

swarm.join('wowcool')

swarm.leave('wowcool')

// If you want to add auto-reconnect logic
swarm.on('disconnected', () => {
	swarm.reconnect(websocket('ws://localhost:4200'))
})

setTimeout(() => {
	swarm.close()
}, 10000)

Check out demo/index.js for an example of how this can be used with hyperdrive.

Protocol

Sent to the server

  • connect
  • join(discoveryKey)
  • leave(discoveryKey)

Sent from the server

  • streamOpen(streamID)

Sent from either end

  • streamData(streamId, data)
  • streamClose(streamId)

Behind the scenes

  • Take a discovery-swarm instance
  • When getting a new connection
    • Find out how many clients want it's advertising keys
    • If only one exists, proxy the connection to it
    • I multiples exist, create new connections per client and proxy them
  • Client side will get streams and should do handshaking on them themselves