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

@unityevolv/ofiskit-realtime-core

v0.2.0

Published

The office engine: presence, moves, status, lock and knock, snapshots and diffs, and WebRTC signalling, over one socket.

Readme

@unityevolv/ofiskit-realtime-core

The office engine: presence, moves, status, lock and knock, calls and WebRTC signalling, over one socket.

Every rule lives here, and none of them knows what it is running on. The engine talks to a Transport, asks its adapters every permission question, and sends snapshots and diffs with a sequence number, so a client that misses one knows to ask for a fresh snapshot.

import { createRealtimeServer } from '@unityevolv/ofiskit-realtime-core'

const realtime = createRealtimeServer({
  httpServer,
  officeId,
  store,
  identity,
  templates,
  limiter,
  provider,
})

Two entry points:

  • . — the above, plus the Socket.IO server and the TURN credentials, which need Node.
  • ./portable — the engine, the provider interface and the protocol, with no Socket.IO and no node:crypto, for a host that is not a Node process. The demo uses it to run the whole office inside a browser tab.

Calls go through an RtcServerPlugin. The built-in one is peer-to-peer and has no media server at all; swapping in another provider is a plugin here and an adapter on the client, and no change to any rule above them.

Licence

AGPL-3.0-only. The interface packages (ofiskit-template, ofiskit-presence-store and ofiskit-adapters) are Apache-2.0, so building against the interfaces is not a licensing decision even though extending this is.

Part of ofiskit: a virtual office you can run yourself. Try the demo.