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

wsss

v1.0.1

Published

websocket shared-state server

Downloads

2

Readme

#WSSS - Websocket Shared State Simple websocket server that allows clients to subscribe to updates and arbitrarily update a shared JSON blob.

Quick start

From command line:

npm install
npm start [PORT_NUMBER] # defaults to 8000

From nodejs

require('wsss')(PORT_NUMBER) // defaults to 8000

How it works

Client randomly generates an id for itself, and connects to a named 'room' by sending a ws message like:

    { "id": "af5ef05ebab5447b71be9"
    , "roomName": "room 101"
    }

If the room already exists, then the current state of the room will be sent back to the client. For example

    { "name": "room 101"
    , "version": "ec10de375cd3be59"
    , "state": 
      { "arbitrary": "json"
      , "that": ["somebody put here", "previously"]
      }
    }

If the room does not exist, it will be created and the state will be initialized to an empty JSON object. For example:

    { "name": "room 101"
    , "version": "91efca9fabc35bee"
    , "state": {}
    }

To update the state, send your id, the roomName, the current 'version' of the room, and an 'update', a JSON blob to replace the current state.

    { "id": "af5ef05ebab5447b71be9"
    , "roomName": "room 101"
    , "version": "91efca9fabc35bee"
    , "update": { "message": "Richard was here" }
    }

If the provided version matches the version on the server, a new 'version' will be randomly generated and the new state will be sent to all clients who have connected to the room.

    { "name" : "room 101"
    , "version": "cf2e7131ffbac447"
    , "state": { "message": "Richard was here" }
    }

If the provided version doesn't match, the state will not be updated and an error will be sent to the client which attempted the update, along with the most up-to-date state/version of the room.

{ "error": "wrong version"
, "data": 
  { "name" : "room 101"
  , "version": "70a729dd590bb8b5"
  , "state": { "message": "Griselda was here before Richard. Nya nya."}
  }
}

That's it!