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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@bg-dev/simple-peerjs

v0.2.1

Published

Simple Peerjs

Downloads

4

Readme

Simple Peerjs

npm version npm downloads License

PeerJS wraps the browser's WebRTC implementation to provide a complete, configurable, and easy-to-use peer-to-peer connection API. Equipped with nothing but an ID, a peer can create a P2P data or media stream connection to a remote peer.

The intended goal behind this work is to more simplify the usage by auto-handling of data connections and providing a global API to reference connections and trigger events.

Setup

Install the package:

npm i @bg-dev/simple-peerjs

Instantiate a new SimplePeer instance and set config options which extends Peer options:

const simplePeer = new SimplePeer({
  rmVideoElId: "rm-video",
  lcVideoElId: "lc-video",
  callingTimeoutMs: 15000,
  connectIntervalMs: 10000,
});
  • rmVideoElId: id of video element for the remote stream.
  • lcVideoElId: id of video element for the local stream.
  • callingTimeoutMs: timeout in ms of a media call.
  • connectIntervalMs: interval in ms of reconnect for a data connection.

Usage

When the local Peer id (your id) is available, for example on login, initialize simplePeer. This will connect the local peer to the Peer server.

simplePeer.init(lcPeerId);

When the local peer id is no longer available, for example on logout, terminate simplePeer. This will disconnect the local peer from the Peer server and clear data connections.

simplePeer.end();

When a remote peer is available register it by their Peer id. This will connect the local peer to the remote peer with reconnection set by connectIntervalMs.

simplePeer.addPeerData(rmPeerId);

To get the added Peer data:

simplePeer.getPeerData(rmPeerId);

When a remote peer is no longer available unregister it. This will disconnect the local peer from the remote peer and clear the data connection.

simplePeer.removePeerData(rmPeerId);

To send data to the remote peer:

simplePeer.getPeerData(rmPeerId).sendData("data");

To start a media call with the remote peer. The call will be auto-terminated when not accepted during timeout set by callingTimeoutMs.

simplePeer.peerMedia.startCall(rmPeerId);

To accept an incoming media call:

simplePeer.peerMedia.acceptCall();

To end an active or pending media call:

simplePeer.peerMedia.endCall();

Events

The simplePeer triggers the following events that you can listen to via simplePeer.hooks.hook().

  • media:call: triggered on media call request which can be rejected by throwing an error.
  • data:connection: triggered on data connection request which can be rejected by throwing an error.
  • data:received: triggered on data reception.
  • media:status: triggered on change of status of the media call.
    • active: media is streaming.
    • waiting: pending on the initial peer.
    • calling: pending on the other peer.
    • inactive: otherwise.

Development

# Install dependencies
pnpm i

# rename .example.env to .env

# Run peer server
pnpm peer

# Develop with the playground
pnpm dev

License

MIT License