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

@overseer-studio/sdk

v0.6.0

Published

Build extensions for Overseer Studio

Readme

Overseer Studio SDK

Build, publish, and develop plugins for Overseer Studio.

What's in this package

  • CLI (overseer) — scaffold, build, and publish plugins to the marketplace
  • Library — runtime API for extensions (events, toasts, shortcuts)

Prerequisites

Node.js and npm.

Setup

Install the SDK as a dev dependency in your plugin project:

npm install --save @overseer-studio/sdk

Add the overseer CLI to your package.json scripts:

{
  "scripts": {
    "overseer": "overseer"
  }
}

Run CLI commands through npm:

npm run overseer -- login
npm run overseer -- init
npm run overseer -- build
npm run overseer -- publish

Quick start

npm run overseer -- login
npm run overseer -- scope claim @your-name
npm run overseer -- init
# ... build your extension files ...
npm run overseer -- publish

See the full developer documentation for a step-by-step tutorial and command reference.

Library

If you're building a bundled extension with a JavaScript build step, import the SDK directly:

import { onReady, sendEvent, subscribe, unsubscribe } from '@overseer-studio/sdk';

const destroy = onReady(({ detail: { config, extensionId, language } }) => {
  sendEvent('my-event', { data: 'value' });

  subscribe('another-event', (payload) => {
    console.log(payload);
  });
});

// Call when your extension is torn down
destroy();

Toasts

import { toast } from '@overseer-studio/sdk';

toast.success('Done!', 'Your action was successful.');
toast.error('Oops', 'Something went wrong.');
toast.warning('Heads up', 'Check this out.');
toast.info('FYI', 'Here is some information.');

Shortcuts

Define shortcuts in your extension manifest, then listen for them:

import { onShortcut } from '@overseer-studio/sdk';

onShortcut('next-turn', () => {
  // advance to the next turn
});

State

Persist runtime state across sessions — for example, which monster is currently selected. Each tile gets its own keyed store; setState saves a value, getState reads it back, and null clears a key.

import { onReady, getState, setState } from '@overseer-studio/sdk';

type SelectedMonster = { id: string; name: string };

onReady<{}>(async ({ detail: { state } }) => {
  const initial = state?.selected as SelectedMonster | null;
  render(initial);
});

function select(monster: SelectedMonster) {
  setState<SelectedMonster>('selected', monster);
}

async function loadLater() {
  const current = await getState<SelectedMonster>('selected');
}

TypeScript

Full TypeScript definitions are included:

type MyConfig = {
  url: string;
  label: string;
};

const destroy = onReady<MyConfig>(({ detail: { config } }) => {
  console.log(config.url);   // typed
  console.log(config.label); // typed
});

License

ISC — 2025–2026 © Infinite Turtles, LLC.