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-dev

v1.4.3

Published

Build, validate, package, install and watch Komari plugins

Readme

@komari-monitor/plugin-dev

Build and install tools for Komari plugin projects.

The package is intended to be used through npm scripts in a generated plugin project. It does not require a globally installed Komari CLI.

{
  "scripts": {
    "check": "komari-plugin-dev check",
    "build": "komari-plugin-dev build",
    "pack": "komari-plugin-dev pack",
    "plugin:install": "komari-plugin-dev install --enable",
    "dev": "komari-plugin-dev dev"
  },
  "komari": {
    "source": "src/plugin.ts",
    "files": ["pages/dist"]
  }
}

The manifest entry is built with esbuild as an IIFE, while server remains an external CommonJS module supplied by Komari.

Connection settings can be supplied without putting credentials in the manifest:

{
  "serverUrl": "http://127.0.0.1:25774",
  "apiKey": "...",
  "language": "en"
}

Save that as komari.local.json and add it to .gitignore, or use KOMARI_SERVER_URL and KOMARI_API_KEY environment variables.

dev uploads plugin packages through Komari's chunked upload API. A running plugin is unloaded, replaced, and loaded again by the server, so the plugin's enabled state and persistent storage are preserved. dev also asks the server to enable the plugin after the first install; use --approved when the manifest requests permissions that require approval. install only enables the plugin when passed --enable.

dev follows the plugin's runtime log buffer through the existing admin:getPluginLogs RPC and prints new lines as they arrive. It polls every 500 ms by default; use --no-logs to disable following or --log-interval 1000 to change the interval. The server only keeps a bounded buffer, so this is intended for development feedback rather than permanent log storage.

The CLI supports Chinese and English. Set --lang zh-CN or --lang en, or set KOMARI_LANG. Generated projects store the selected language in komari.local.json.

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