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

webrtc-mesh

v0.9.8-beta

Published

using a signaler, mesh between node, browsers and other applications

Readme

webrtc-mesh

** BETA Release API in the work, Subject to Change **

What does it do??

Prerequisite Disclaimer

WebRTC allows direct communication between RTC capable Peers (usually browser to browser), thanks to the modern Robinhood Style of Coding (aka take from the geniuses and give to the masses) we can make node talk to webRTC peers. (Shoutout to my dependency contributors @theturtle32, @markandrus and @modeswitch)

The sauce

Using your websocket signaling server (echo server to all connected peers for sdp exchange) do automagically connect all clients running this lib with a network of datachannels

API - Beta

Initialize

const Mesh = require('webrtc-mesh').Mesh;

var config = {
  url: 'wss:websocket.url.server:port/',
  key: 'appKey or Token for message filtering', //optional, default is 'mesh'
  debug: false, //optional, default is false
}

var mesh = Mesh(config);

mesh.pipe( (ev) => { //handle incoming data
  console.log('we got some data from another peer', ev.data)
  });

mesh.sendToAll( arrayBuffer(12) ) // or even just 'string of Json'

Initialize as Stream

var Mesh = require('webrtc-mesh').Mesh;

var config = {
  url: 'wss:websocket.url.server:port/',
  key: 'appKey or Token for message filtering', //optional, default is 'mesh'
  debug: false, //optional, default is false
}

var mesh = Mesh(config)

var meshedStream = mesh.getStream();
mesh.pipe(meshedStream.push.bind(meshedStream));

process.stdin.pipe(meshedStream).pipe(process.stdout);

Utilities

mesh.getPeerList() // returns a map of connected Peers with KEY: peerID Value: object with {status:connectionStatus, conn:reference to Peer Connection, channel: reference to data channel}
mesh.getPeer(peerId) // returns a specific peer from the map
mesh.getPeerId() //return your peerId
mesh.printPeers() // console print for quick check against connection status
mesh.sendToAll(buffer || blob || string) //send to all peers
mesh.onNewPeer( function ) // register a function to receive the 'onOpen' event of a new data channel