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

peer2peertc

v1.0.12

Published

peer to peer video and audio, based on webrtc

Downloads

17

Readme

peer to peer , based on webrtc

Be sure to use HTTPS protocol or localhost, otherwise the demo will not work properly

github

Simple WebRTC video, voice, and data channels;

The peer2peerRTC is separated from websocket; you can customize your signaling service.

features

  • supports video/voice streams
  • supports data channel

usage

you can install with npm ,or import like demo

npm install gun-p2prtc

This example create two peers in separated web page.

In a real-world application, The sender and receiver Peer instances would exist in separate browsers. A "signaling server" (usually implemented with websockets) would be used to exchange signaling data between the two browsers until a peer-to-peer connection is established.

api

new P2pRtc(option)

If option is specified, then the default options (shown below) will be overridden.

const option = {
    rtcConfiguration: null,
    initiator: false,
    offerOptions: {offerToReceiveAudio: 1, offerToReceiveVideo: 1},
    answerOptions: {},
    constraints: {audio: true, video: true},
    localStream: null
}
const peer = new P2pRtc(option);

The options do the following:

  • rtcConfiguration: custom webrtc configuration (used by RTCPeerConnection constructor);
  • initiator: set to true if this is the initiating peer
  • offerOptions: custom offer options (used by createOffer method)
  • answerOptions: custom answer options (used by createAnswer method)
  • constraints: custom stream options (used by getUserMedia method)
  • localStream: if video/voice is desired, pass stream returned from getUserMedia

peer.signal(data)

Call this method whenever the remote peer SDP message received.

peer.mute(kind)

string <video | audio>. close local audio or close local video

peer.unmute(kind)

string <video | audio>. open local audio or open local video, and remote peer will received.

peer.getStats()

provide statistics about either the overall connection

peer.send(text)

send text over datachannel

peer.leave()

peer leave.

events

localStream

peer.addEventListener('localStream', data => {
    localVideo.srcObject = data.stream
})

offer

peer.addEventListener('offer', offer => {
    ws.send(JSON.stringify(offer))
})

answer

peer.addEventListener('answer', answer => {
    ws.send(JSON.stringify(answer))
})

icecandidate

peer.addEventListener('icecandidate', event => {
    if (event.candidate) ws.send(JSON.stringify({type: 'icecandidate', candidate: event.candidate}))
})

remoteStream

 peer.addEventListener('remoteStream', event => {
    remoteVideo.srcObject = event.remoteStream;
})

dataChannel-ready

peer.addEventListener('dataChannel-ready', () => {
    // now you can use dataChannel send message
});

message

peer.addEventListener('message', (event) => {
    console.log('receive text => ', event.data)
});