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

presence-store

v0.120.0

Published

Client side presence channel handler

Readme

PresenceStore — Client side presence channel handler

The purpose of this class is to connect to the reflector service and provide a consistent view of what everybody else on the channel is "doing", i.e. their state. This supports the real time presence experience in Sanity.

Usage

import PresenceStore from '@sanity/presence-store'
import Reflector from '@sanity/reflector-client'
import myConfiguredSanityClient from './myConfiguredSanityClient'

const presenceStore = new Presence(new Reflector(myConfiguredSanityClient).connect('channelName'))

// Subscribe to state changes about all other users on the channel
presenceStore.presence.subscribe(allTheirStates => {
  // Called with an array of all known states whenever it changes
  console.log(allTheirStates)
})

// Report my state to the other clients on the channel
presenceStore.reportMyState({
  location: "/fnah",  // The format of state reports is app-specific, can be any JSON'able object, but keep it
  activity: "editing" // short and sweet. At the time of writing we don't know how the Sanity studio will use it.
})

// Do this to allow the presence store to notify the others that we left. Uses
// navigator.sendBeacon to get the message out even though the window is closing.
window.addEventListener("beforeunload", function(e){
  presenceStore.close()
}, false);

Format of state reports

The reports from the presence subscription (i.e. allTheirStates as seen above) will look someting like this:

[
  {
    identity: "<a sanity identity>",
    session: "<an UUID to identify the browser window>",
    // and now whatever this client reported to reportMyState:
    location: "/fnah",
    activity: "editing"
  },
  // more of these ...
]

The order of the reports is consistent between calls, the object identity of each report is identical until it changes, and is always new when it does change.

You don't see your own state reported in this window in the list, but you will see state reported for your identity in other windows.