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 🙏

© 2025 – Pkg Stats / Ryan Hefner

redux-rxjs-socket.io

v1.0.1

Published

connect socket.io to redux when using redux-observable

Readme

redux-rxjs-socket.io

Helper functions to connect socket.io to redux, when using redux-observable.

Mappers

This library lets you define mappers from socket events to redux actions, and redux actions to socket events. The mappers you define are maps, that return a function that may return a value/array or a stream.

Event to Action Mappers

Below is a sample definition of socket to redux actions.

{
    // custom event that is triggered if you use the #register method and socket is registered
    [RegisterHelper.Symbols.SOCKET_REGISTER]: () => actions.createSocketUserConnect(),
    // custom event that is triggered when the subscription is stopped
    [RegisterHelper.Symbols.SOCKET_UNREGISTER]: () => actions.createSocketDisconnect(),
    // some custom events with data, that are emitted by the client/server socket
    ping: ({ time }) => actions.createPingAction(time),
    // you can also use the latest game state, when creating actions, can return streams
    test: ({ key }, gameState) => from(promise).pipe(map(() => actions.createTestAction(key, gameState.blaBla))),
}

Action to Emit Mappers

Below is a sample definition of mapping redux actions into emitted events.

(mapperUserId) => ({
    // on some action, create an event
    [ActionTypes.UserConnected]: ({ userId }, state) => {
       return userId !== mapperUserId
           ? [ { event: 'other_user', data: { userId, leaderboard: state.leaderboard } } ]
           : [];
    },
})

Methods

  • generateActionStreamCreator = (mapperDefinition) => (socket, state$, outsideEvent$) given a mapper definition, returns a function, that will return a action stream when given a socket, state stream and an custom outsideEventStream. When the returned stream is unsubscribed, the event register events on sockets will be unregistered.
  • generateEmitStreamCreator = (mapperDefinition) => (action$, state$) given a mapper definition, returns a function, that will return a event stream when given redux action stream and a redux state stream.
  • register = (eventToActionMapper, actionToEventMapper) => (socket, action$, state$, storeDispatch) when given event and action mapper definitions, returns you a function that will register a socket to a redux store. You just need to give socket, action$, state$ and the store dispatch function.