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

@komari-monitor/plugin-sdk

v1.4.3

Published

TypeScript SDK and runtime helpers for Komari server plugins

Readme

@komari-monitor/plugin-sdk

TypeScript types and small runtime helpers for Komari server plugins.

The package targets Komari's CommonJS goja runtime. It does not add browser APIs or assume a full Node.js implementation.

When permissions.node is enabled in the manifest, the SDK also declares the Komari runtime globals require(...) and __storageDir__ for TypeScript. The storage directory is an absolute path intended for data that should survive plugin rebuilds and reinstalls.

import { definePlugin } from "@komari-monitor/plugin-sdk";

const fs = require("fs");

definePlugin({
  load() {
    console.log(__storageDir__);
    console.log(fs.existsSync(__storageDir__));
  },
});

Add the following to komari-plugin.json to enable manifest completion in VS Code:

{
  "$schema": "./node_modules/@komari-monitor/plugin-sdk/schema/komari-plugin.schema.json",
  "name": "Example",
  "short": "example"
}
import { definePlugin, jsonResponse, server } from "@komari-monitor/plugin-sdk";

definePlugin({
  load() {
    server.route("GET", "/hello", (_req, res) => {
      jsonResponse(res, { ok: true });
    });
  },
});

Known Komari RPC methods have TypeScript parameter and return-value hints:

import { rpc, rpcCatalog } from "@komari-monitor/plugin-sdk";

const nodes = await rpc.call("common:getNodes");
const exists = await rpc.has("public:queryMetrics");
const meta = await rpc.help("common:getNodes");
const declared = rpcCatalog["common:getNodes"];

rpc.call() is for the SDK's typed Komari RPC catalog. Use server.call() for dynamic methods or plugin-owned methods. rpcCatalog contains the declared parameter and return descriptions for the Komari 1.4.x API. rpc.has() checks the method list of the current Komari server without executing that business method; rpc.help() returns its runtime name, parameter metadata, and return description when the server provides them. These calls use server.call() internally and therefore require the allowSystemRPC permission.

The catalog is a snapshot for the Komari 1.4.x compatibility line; rpc.has() remains the runtime authority when the target server has a different set of registered methods.

Repository: https://github.com/komari-monitor/plugin-sdk