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

@horribledashboard/sdk

v0.1.0

Published

Plugin SDK for horrible-dashboard: the plugin contract (definePlugin, panels, widgets, commands, keybindings) and the Vite build preset for plugin authors.

Readme

@horrible/sdk

Plugin SDK for horrible-dashboard — the typed plugin contract and the Vite build preset for plugin authors.

A plugin is an ES module whose default export is definePlugin({ setup }). The host calls setup(host) at boot; whatever you return (panels, widgets, commands, keybindings) is registered into the shell. Plugins are trusted code (Obsidian-style): they run unsandboxed in the app realm.

Writing a plugin

// src/index.tsx
import { definePlugin } from '@horrible/sdk';

export default definePlugin({
  setup(host) {
    return {
      widgets: [
        {
          id: 'my-plugin.greeting',
          title: 'Hello',
          component: () => <p>Hello from a plugin!</p>,
        },
      ],
      commands: [
        {
          id: 'my-plugin.sayHello',
          title: 'My Plugin: Say hello',
          run: () => host.openPanel('dashboard.home'),
        },
      ],
    };
  },
});

Every contributed id must be namespaced under your plugin id (<pluginId>.<name>) — the loader rejects anything else.

Building

Use the bundled Vite preset. It marks react, react/jsx-runtime, and @horrible/sdk external and rewrites them to host-served shim URLs, so every plugin shares the host's React instance and SDK runtime. Bundling your own React breaks hooks — don't bypass the preset.

// vite.config.ts
import { defineConfig } from 'vite';
import { horriblePluginViteConfig } from '@horrible/sdk/vite';

export default defineConfig(horriblePluginViteConfig({ entry: 'src/index.tsx' }));

vite build produces dist/index.js — a few kB, since everything heavy is external. Add a horrible-plugin.json manifest next to it and the package is installable from a catalog:

{
  "id": "my-plugin",
  "name": "My Plugin",
  "version": "0.1.0",
  "description": "What it does.",
  "author": "you",
  "entry": "dist/index.js",
  "sdkVersion": 1,
  "requiredCapabilities": [],
  "permissions": []
}

The host handle

setup(host) receives the only door back into the shell:

  • host.api — backend HTTP client (get/post/put/del, relative to /api)
  • host.storage — per-plugin key-value storage, persisted server-side
  • host.subscribeChannel(channel, handler) — the shared /ws socket
  • host.openPanel(panelId) / host.runCommand(commandId)
  • host.hasCapability(capability)

See the plugin SDK architecture doc for the full design, and examples/plugins/hello-widget for a complete working plugin.