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

xdev-plugins

v1.0.1

Published

Bundle manager for pi/omp plugins: batch modes (caveman, ponytail, rtk), pinned upgrades, health checks. CLI + /xdev slash command.

Readme

xdev-plugins

Bundle manager for Oh My Pi (omp/pi) plugins: installs, pins, checks, and upgrades a fixed set of plugins. Ships as an npm CLI (xdev) plus an in-session /xdev command.

What xdev does — and nothing else:

  • installs missing constituents
  • upgrades them to latest, rewriting its pins
  • reports pinned / installed / latest versions
  • self-upgrades

Plugin toggles and modes are the plugins' own business: use /caveman, /ponytail, /rtk directly.

Bundled plugins

| Plugin | Role | |---|---| | pi-caveman | terse replies | | @dietrichgebert/ponytail | lazy/minimal-code guidance | | pi-rtk-optimizer | compact shell output |

Install

Requires Node 18+ and Oh My Pi.

npm install -g xdev-plugins          # the `xdev` CLI
omp plugin install npm:xdev-plugins  # the /xdev command (or `omp plugin link <path>` for dev)
xdev install                         # install bundled constituents (missing only)

Restart omp (or run /reload-plugins).

Commands

In-session

| Command | Effect | |---|---| | /xdev / /xdev status | per-plugin versions: pinned / installed / latest | | /xdev upgrade [name ...] | update plugins to latest, rewrite pins, self-upgrade, reload; --dry-run previews | | /xdev doctor | installed-vs-pin report |

CLI (xdev)

xdev install                 # install missing constituents
xdev upgrade [name ...]      # update to latest, rewrite pins; --dry-run
xdev status [name ...]     # pinned / installed / latest table
xdev doctor                  # per-constituent health + `omp plugin doctor`
xdev version

Flags: --dry-run, --scope user|project|marketplace (accepted; npm installs are user-scope in omp).

How it works

  • Pins live in xdev-manifest.json in the omp agent dir (~/.omp/agent/), seeded from the bundled manifest.json on first run. upgrade rewrites pins; rollback = revert pins, reinstall the old versions.
  • Version changes run only through omp's own installer (omp plugin install npm:<name>@<version>), keeping its validation and rollback. The bundle never touches node_modules directly.

Extending the bundle

Edit manifest.json, bump the package version, publish:

{ "name": "pi-caveman", "pin": "1.0.8" }

Add or drop constituents freely; existing state manifests reseed missing entries automatically.

Development

node --test              # unit tests (agent-dir isolated)
npm publish            # release = version bump + publish

License

MIT