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

@tomradex/plugin-cli

v0.2.30

Published

tomrade-plugin: scaffold, build, test in a sandbox, check and pack a Tomrade plugin

Readme

@tomradex/plugin-cli

tomrade-plugin builds, tests and packs a Tomrade plugin.

tomrade-plugin init my-plugin --id you/my-plugin   # a plugin that builds, tests and loads as it is
tomrade-plugin dev                                  # rebuild on every change; in Tomrade: Settings → Plugins → Load folder
tomrade-plugin test                                 # src/test.ts against a throwaway project, in a sandbox
tomrade-plugin check                                # what someone installing it will see
tomrade-plugin pack                                 # a .tomrade-plugin file anyone can install

build bundles src/index.ts into one readable file, dist/index.js, leaving @tomradex/plugin-sdk and zod to Tomrade. test and check run the plugin in a child process under Node's permission model: it reads only the plugin's folder and the CLI's own runtime, writes only a temporary directory, and cannot start programs.

Apache-2.0, like @tomradex/plugin-host installed alongside it and the rest of Tomrade. What you build with the CLI is yours, under any license you choose.