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

p2ply

v0.2.1

Published

A browser-first, self-hostable WebRTC peer-to-peer networking library for TypeScript.

Readme

P2Ply

Peer-to-peer, made simple. Messaging and file sharing for TypeScript apps, built on WebRTC.

P2Ply connects browsers (and Node.js) directly to each other. You get typed messages, request/response, and verified file transfer without writing any WebRTC signaling code yourself. A small signaling server, which you host, introduces peers to each other. After that, your data flows peer-to-peer and never passes through the server.

  Browser A  ◄──── WebRTC DataChannel (your data) ────►  Browser B
       │                                                    │
       └─────────►  Signaling server (handshake only) ◄─────┘

Live demo → Join a room, then open the invite link in another tab or on another device. You can chat, drag and drop files, and press Rebuild connection mid-transfer to watch it resume. The free demo server sleeps when idle, so the first connection can take up to a minute.

Features

  • Rooms and discovery: join a room and see who else is there.
  • Messaging: typed JSON messages, broadcast, optional delivery acknowledgements, request/response.
  • File transfer: chunked, with progress, cancellation, and SHA-256 integrity checks.
  • Reliability: dropped connections reconnect automatically, file transfers resume where they stopped, and messages sent during a drop are delivered after it. Bounded queues and timeouts everywhere.
  • Diagnostics: connection state, bytes, round-trip time, and whether traffic is direct or relayed.
  • Self-hosted: the signaling server is included. There is no paid service and no API key.
  • Secure defaults: validated protocol, rate limits, origin checks, and auth hooks.

Try it in 1 minute

Requires Node.js 20.19+ and pnpm (corepack enable).

pnpm install
pnpm dev               # terminal 1: starts the signaling server on ws://localhost:8787
pnpm dev:playground    # terminal 2: opens the demo UI on http://localhost:5173

Open http://localhost:5173, join a room, and open the invite link in a second tab. The tabs connect automatically; you can chat, send files, and view connection details.

Install

pnpm add p2ply          # or: npm install p2ply

Usage

import { P2Ply } from 'p2ply';

const mesh = new P2Ply<{ text: string }>({
  signalingUrl: 'ws://localhost:8787',
});

// A new peer appeared in the room: open a direct connection to it.
mesh.on('peer:join', ({ peerId }) => {
  mesh.connect(peerId).catch(console.error);
});

// The connection is ready: say hello.
mesh.on('peer:state', ({ peerId, state }) => {
  if (state === 'connected') mesh.send(peerId, { text: 'Hello!' });
});

// A message arrived from a peer.
mesh.on('message', ({ peerId, data }) => {
  console.log(peerId, 'says', data.text);
});

mesh.on('error', (error) => console.error(error.code, error.message));

await mesh.start(); // connect to the signaling server
await mesh.join('my-room'); // join a room

// later
await mesh.close();

Both peers may call connect() at the same time; P2Ply handles the collision for you.

Send a file

// Receiver: accept incoming files
mesh.on('file:offer', ({ metadata, accept }) => {
  console.log('Incoming', metadata.name, metadata.size, 'bytes');
  accept();
});
mesh.on('file:complete', ({ result }) => {
  // result.blob holds the file, and its SHA-256 has already been verified
});

// Sender
const transfer = await mesh.sendFile(peerId, fileInput.files[0]);
await transfer.completion;

Request / response

// Peer B
mesh.on('request', ({ data, respond }) => {
  const { a, b } = data as { a: number; b: number }; // validate untrusted input in real code
  respond({ sum: a + b });
});

// Peer A
const answer = await mesh.request(peerB, { a: 2, b: 3 }); // { sum: 5 }

Node.js

Install the optional WebRTC adapter (pnpm add @roamhq/wrtc), then use await NodeP2Ply.create(options) from p2ply/node. Same API as P2Ply. See Node.js.

Main API

| Method | What it does | | ------------------------------------- | ------------------------------------------------------ | | start() / close() | Connect to / disconnect from everything | | join(room) / leave(room) | Enter or leave a room | | getPeers() / getPeer(peerId) | List peers you can see and their state | | connect(peerId) | Open a direct connection to a peer | | send(peerId, data, { acknowledge }) | Send a message | | broadcast(data) | Send to every connected peer | | request(peerId, data) | Send and wait for a reply | | sendFile(peerId, file) | Send a file | | cancelTransfer(transferId) | Stop a file transfer | | reconnectPeer(peerId) | Rebuild a peer connection now (also automatic) | | reconnectSignaling() | Reopen the server connection and rejoin rooms | | getDiagnostics() | Connection stats for debugging | | on(event, fn) | Subscribe to an event; returns an unsubscribe function | | once(event, fn) / off(event, fn) | Listen once / remove a listener |

Events: peer:join, peer:leave, peer:state, signaling:state, message, request, file:offer, file:progress, file:complete, file:error, error.

Read the full guide → It covers every option, delivery guarantees, the server, STUN/TURN, security, and troubleshooting.

Run your own signaling server

npx p2ply-server                                   # after installing the package
P2PLY_PORT=8787 P2PLY_ALLOWED_ORIGINS=https://myapp.com npx p2ply-server
docker build -t p2ply-signaling . && docker run -p 8787:8787 p2ply-signaling

Health check: GET /health. For authentication and room rules, create the server in code (see examples/self-hosted-server and the guide).

Connecting across different networks? Localhost and LAN work out of the box. Over the internet, add a STUN server, and a TURN server for strict firewalls. See STUN and TURN.

Examples

Start the server with pnpm dev first, then run an example:

| Command | Example | | --------------------------------------------- | ------------------------------------------------------------ | | pnpm dev:playground | Full demo UI: chat, files, reconnection (localhost:5173) | | pnpm example:node | Node.js terminal chat (run in two terminals) | | pnpm example:custom | Typed messages with runtime validation (Node) | | pnpm example:reconnect | Automatic peer reconnection (Node) | | P2PLY_AUTH_TOKEN=secret pnpm example:server | Signaling server with token auth (run instead of pnpm dev) |

Contributing

See CONTRIBUTING.md for setup, checks, and the source layout. Report security issues privately as described in SECURITY.md.

Limitations

  • Full mesh: best for small groups (tens of peers).
  • Tested in Chromium and Node.js; Firefox and Safari are not yet tested.

See the full list.

License

MIT