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

web-peer

v0.1.3

Published

Easy way to use WebRTC

Readme

web-peer

Easy way to use WebRTC

What can do

  • Send MediaStreams (audio, video)
  • Send messages
  • Send files (< 200mb for now)

Install

npm install web-peer

How to use

Web-peer provide only client-side interface for WebRTC. You should use some signaling mechanism.

Example of using with socket.io:

var socket = require('socket.io-client').connect(window.location.host),
    Peer = require('web-peer'),
    peer = new Peer();


peer.on('error', console.error.bind(console));
peer.on('sync', socket.emit.bind(socket, 'sync'));
socket.on('sync', peer.sync.bind(peer));

and server.js

var io = require('socket.io');

io.sockets.on('connection', function (socket) {
    socket.on('sync', function (data) {
        socket.broadcast.emit('sync', data);
    });
});
io.listen(<your port>)

API

Peer()

creates new peer

var peer = new Peer();

Peer#sync(options)

Two peer should sync with some signaling mechanism. This is only function needed for that.

Any peer emit sync event when it require to signale to another peer

peer.on('sync', function (options) {
    someHowSendToAnotherPeer(options);
});

another peer waing until sync function will be callen

someHowOnGetSyncMessage(function (options) {
    peer.sync(options);
});

Peer#send(messageName, messageData)

send message

peer.send('to-chat', {name: 'boss'});

on another side

peer.messages.on('to-chat', function (info) {
    console.log('%s joined to chat', info.name); // boss joined to chat
});

Peer#addStream(mediaStream)

send MediaStream

getUserMedia({ audio: true, video: true }, function (stream) {
    peer.addStream(stream);
}, console.error.bind(console));

on another side

peer.on('stream', function (mediaStream) {
    var video = document.querySelector('video');
    video.src = URL.createObjectURL(mediaStream);
    video.play();
});

Peer#sendFile(file)

send File

var input = document.querySelector('input[type=file]');

input.addEventListener('change', function () {
    if (input.files.length) {
         peer.sendFile(input.files[0]);
    }
});

on another side // file is instanceof private constructor FileStream which makes easier work with file

peer.on('file', function (file) {
    // file will load only after you allow it
    file.load();

    file.on('progress', function (progress) {
        document.querySelector('progress').value = progress;
    });

    file.on('url', function () {
        var link = document.querySelector('a');
        a.download = file.name;
        a.innerHTML = file.name;
        a.href = file.url;
    });
});

Peer#close()

close connection

Peer events

  • error any error
  • stream new incoming MediaStream
  • file new incoming file
  • sync request to use signaling mechanism to send data to another peer
  • close when connection is closed
  • disconnect when remote peer is disconnected

FileStream#load()

start load file

FileStream#getBlob()

get file blob

FileStream#url

url to filesystem file location

FileStream#name

file name