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

@wp-operations/wp-ide

v0.2.0

Published

Project and monorepo tooling for wp-operations: .local data convention, project resolution, blueprint runner.

Readme

@wp-operations/wp-ide

Project and monorepo tooling for wp-operations. Library, no CLI — wp-app serves, wp-ops orchestrates, wp-ide knows where things live.

The .local convention

All runtime data for a repository — SQLite databases, uploads, per-app wp-content — lives in one gitignored .local/ directory at the repo root. Delete it and every app resets. Nothing hides in the user's home folder.

<repo>/.local/
└── wp-content/
    ├── my-theme/       wp-content + SQLite db for the my-theme app
    └── my-plugin/

API

import {
  resolveProject,     // walk up to repo root, read wp-operations.json
  localPath,          // localPath(root, 'wp-content', 'my-app')
  ensureLocalDir,     // same, but creates it
  appServerOptions,   // build wp-app startServer options with .local wpContentPath
  runBlueprint,       // run blueprint steps against a running wp-app php instance
} from '@wp-operations/wp-ide';

Start an app with its data in .local instead of ~/.wp-app:

import { startServer } from '@wp-operations/wp-app';
import { appServerOptions, runBlueprint } from '@wp-operations/wp-ide';

const options = appServerOptions('./apps/my-theme', { wp: 'classicpress' });
const { php, url } = await startServer(options);

await runBlueprint(php, {
  steps: [
    { step: 'defineWpConfigConsts', consts: { WP_DEBUG: true } },
    { step: 'login', username: 'admin', password: 'password' },
  ],
});

Supported blueprint steps: defineWpConfigConsts, login, activatePlugin, activateTheme, runPHP, writeFile. Unknown steps are reported as skipped, never fatal.

wp-operations.json

Optional repo-root config consumed by resolveProject / appServerOptions:

{
  "php": "8.0",
  "wp": "classicpress",
  "apps": {
    "my-theme": "apps/my-theme"
  }
}

License

GPL-2.0-or-later.