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

@longstoryshort/vtt-sdk

v0.9.0

Published

Embed a longstoryshort.app character sheet in any virtual tabletop via iframe and postMessage

Readme

@longstoryshort/vtt-sdk

Embed a longstoryshort.app character sheet in any virtual tabletop via iframe and postMessage.

How it works

The sheet and your VTT run at different origins. They communicate only via window.postMessage — your code never reads the sheet's DOM, cookies, or auth token.

Your page (your origin)
  └── LSS sheet iframe (longstoryshort.app)
        └── postMessage ──→ your page

Installation

npm install @longstoryshort/vtt-sdk

For Owlbear Rodeo, also install the peer dependency:

npm install @owlbear-rodeo/sdk

Packages

| Import | Contents | |--------|----------| | @longstoryshort/vtt-sdk | Core: protocol types, createBridgeSheetSource, createSheetClient, formatRollMessage, SHEET_IFRAME_SANDBOX | | @longstoryshort/vtt-sdk/owlbear | OwlbearAdapter, ObrAdapter, OBR bootstrap helpers |

Quick start

import { createBridgeSheetSource, SHEET_IFRAME_SANDBOX, formatRollMessage, rollVariant } from '@longstoryshort/vtt-sdk';

// Embed the sheet
const iframe = document.createElement('iframe');
iframe.src = 'https://longstoryshort.app/iframe/characters/list/';
iframe.setAttribute('sandbox', SHEET_IFRAME_SANDBOX);
iframe.setAttribute('allow', 'clipboard-write');
iframe.style.cssText = 'border:none;width:100%;height:100vh;display:block';
document.body.appendChild(iframe);

// Receive rolls
const source = createBridgeSheetSource({
    iframe,
    allowedOrigins: ['https://longstoryshort.app'],
});

source.onRoll((roll) => {
    // wire to your VTT — notification, chat, peer broadcast, etc.
    console.log(formatRollMessage(roll), rollVariant(roll));
});

// cleanup
source.dispose();

Documentation

The full guides — sandbox requirements, protocol reference, utilities, and the annotated bridge/OwlbearAdapter reference — live in the Long Story Short docs, not in this repo:

  • SDK guide — start here regardless of your VTT architecture.
  • Bridge guide — for VTTs that use an extension/plugin model and need a separate static bridge page.

This repo keeps the code: the SDK source, the bridge template, and the deployed Owlbear Rodeo reference bridge below.

Reference bridge — Owlbear Rodeo (D&D 5e)

A deployable bridge for Owlbear Rodeo lives in bridges/dnd/. Deployed automatically to GitHub Pages on every push to master.

Live manifest: https://bridge.longstoryshort.app/dnd/obr/manifest.json

To install in OBR: Extensions → Add extension → paste the manifest URL above.

Bridge template

bridges/_template/ is a minimal copy-and-modify skeleton — iframe embed + createBridgeSheetSource + TODO comments for your VTT's APIs, ready to build with Vite.

Protocol events

| Type | Status | Direction | Description | |------|--------|-----------|-------------| | lss:roll | ✅ stable | sheet → host | A roll result | | lss:manifest | 🧪 reserved | sheet → host | Sheet capabilities at handshake | | lss:command | 🧪 reserved | host → sheet | Inbound ops (adjust HP, toggle condition, …) | | dnd:health | 🧪 reserved | sheet → host | HP after an adjust/set | | lss:group-selected | 🧪 reserved | group-manager page → host | A group was created/picked — persist groupId/code | | lss:group-code | 🧪 reserved | host → sheet | Offer a group to a specific player's sheet | | lss:group-leave | 🧪 reserved | host → sheet | Remove that player from the group the host offered | | lss:group-status | 🧪 reserved | sheet → host | Is this character currently a member of that group |

Reserved events are typed and wired end-to-end, but the bridge-side API is experimental. Subscribe via source.onEvent directly.

The prefix says whose vocabulary the payload speaks: lss: is the platform protocol, shared by every sheet product we ship, and dnd: is reserved for payloads that only make sense for the D&D 5e sheet — such as dnd:health, which carries 5e's own temp-HP model. The system-agnostic route to the same numbers is lss:manifest + lss:command.

The lss:group-* events are "Level 2" — shared rights between players at a table, without adopting the Vortex room hub. See docs/plans/level-2-groups.md for the full flow and why there is no shared-metadata dependency like the Owlbear bridges use.

License

MIT