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

react-with-websocket

v3.1.0

Published

Higher order components for better experience in React with websocket.

Downloads

58

Readme

React withWebSocket

Higher order components for better experience in React with websocket.

Dependabot Status

Usage (with WebSocket from browser)

First, create a WebSocket object (for example, ws) in your (lower as possible) common ancestor of Components that require data from WebSocket, and wrap its children with a <WebSocketContextProvider value={ws}>.

That will be the source of WebSocket for those Components.

For each Component, we need to:

  1. Subscribe to a WebSocket

  2. Provide it a WebSocket

For the first part, we will create a subscription using createSubscription

const withSubscription = createSubscription(
    initState,
    fallbackProps,
    mapStateToProps,
    mapMessageToState,
    mapEventToState,
)

The subscription has a state initialized with initState. When there are new message from WebSocket, you need to mapMessageToState.

It receive a message event, return new state (or a function that map previous state to new state).

Similarly when there are new event like open,close,error, you can mapEventToState but that is optional.

Then you mapStateToProps.

It receive current state (and optionally the WebSocket object) and map it to (some of) your Component's props.

If the props returned from mapStateToProps is falsey, then it will use the value from fallbackProps.

Finally you apply the subscription to Component.

const ComponentWithSubscription = withSubscription(Component)

And the second part, let's feed the result with a WebSocket:

const ComponentWithWebSocketSubscription = withWebSocket(Component)

Then, you can use ComponentWithWebSocketSubscription in place of Component with some props subscribed to WebSocket.

For convenient, createWebSocketSubscription works as createSubscription then withWebSocket.

FOSSA Status