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

redux-rtc

v2.0.0-alpha.5

Published

Peer 2 Peer connected states using Redux and WebRTC

Readme

ReduxRTC

Code Coverage Version Downloads ISC License

Peer 2 Peer connected states using Redux and WebRTC

Demo

Github Demo

Table of contents

Installation

npm install redux-rtc -S

Usage

import { createStore, combineReducers, applyMiddleware } from 'redux'
import { connected, rtc, create, enter } from 'redux-rtc'

Middleware

const middleware = applyMiddleware(connected)

Reducer

const rootReducer = combineReducers({
    rtc: rtc, // Required namespace 'rtc'
    ...
})

Store

const store = createStore(rootReducer, middleware)

Create Room

store.dispatch(create())

Once created the store will contain a token. This token is used in other clients to enter the room

Enter Room

store.dispatch(enter(ROOM_TOKEN))

State

const { rtc } = store.getState()

RTC The current state of the ReduxRTC connection

Properties

  • token: (string) - The unique identifier for the connection
  • room: (object) - The room instance RTCMultiConnection
  • streams: (array[VideoElement]) - All of the connected media elements
  • loading: false (boolean) - The loading status of the room
  • error: 'No Room Found' (string) - Errors will propagate here

Dispatch

By default actions that are dispatched do not propagate to connected clients. To share the actions across all peers the property connected should be added to the action

var setTrue = function () {
    return { 
        type: 'SHARED_BOOLEAN_TRUE',
        connected: true
    }
};
var setFalse = function () {
    return { 
        type: 'SHARED_BOOLEAN_FALSE',
        connected: true
    }
};
var toggleReducer = function (state, action) {
    switch (action.type) {
        case 'SHARED_BOOLEAN_TRUE': return true;
        case 'SHARED_BOOLEAN_FALSE': return false;
        default: return state || false;
    }
}

Since the action is denoted as connected, the Middleware handles posting the message to the connection and the connected peers recieve the action and dispatch to their cooresponding stores.

Conclusion

Dependencies