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

@graph-state/plugin-ws

v0.2.0

Published

> Plugin for connect socket server to @graph-state. Work with Socket.io and WebSocket.

Downloads

4

Readme

@graph-state/plugin-ws

Plugin for connect socket server to @graph-state. Work with Socket.io and WebSocket.

Installation

npm i @graph-state/core @graph-state/plugin-ws

or

yarn add @graph-state/core @graph-state/plugin-ws

Get started

import io from 'socket.io-client';
import { createState } from '@graph-state/core';
import wsPlugin from '@graph-state/plugin-ws';

// Create socket
const socket = io('path to server');

// Apply plugin
export const graphState = createState({
  plugins: [
    wsPlugin(socket),
  ],
});

Now each event from socket will populate graphState. Server acts as source of truth. For mutations server need return graph-based object.

Example server response

// server

// That emit update User graph or create new
io.emit('anyEventName', {
  _type: 'User',
  _id: 'userId',
  name: 'testUser'
})

WebSocket server response

socket.send(JSON.stringify({
  eventName: 'anyEventName',
  data: {
    _type: 'User',
    _id: 'userId',
    name: 'testUser'
  }
}))

Transforms

If you use socket server which you can control and adaptive server response. Use transforms.

import { isGraph } from '@graph-state/core'

export const graphState = createState({
  plugins: [
    wsPlugin(socket, {
      transforms: {
        eventName(cache, value) {
          // You can modify input event

          if (!isGraph(value)) {
            // Return graph
            return {
              _type: 'User',
              _id: 'userId', // Attention!! Dot't generate id inside transform.
              anyData: 'data'
            }
          }
          
          return null
        }
      }
    }),
  ],
});

Don't generate id inside transform because socket server is alone but many clients and each client had uniq id for self session. You can build uniq key by incoming data.

wsPlugin(socket,
  {
    transforms: {
      eventName(cache, value) {
        if (!isGraph(value)) {
          return {
            _type: 'User',
            _id: `user-${someUniqFields}`,
            anyData: 'data'
          }
        }

        return null
      }
    }
  }),

Effects

Effect need for side effects of events.

export const graphState = createState({
  plugins: [
    wsPlugin(socket, {
      effects: {
        eventName(cache, value) {
          // do somithing
          cache.invalidate('User:userId')
        }
      }
    }),
  ],
});