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

@codenanny/plugkit

v0.4.0

Published

Tiny plugin contract for modular Express apps. Mount routers, share events, declare sqlite schemas, contribute to nav. Used by codenanny.

Readme

@codenanny/plugkit

Tiny plugin contract for modular Express apps.

plugkit is a ~150-line contract that lets you build modular Express applications where each module declares its own:

  • Express router (mounted by the host)
  • sqlite schema migrations (run automatically)
  • Event bus subscriptions + emissions (shared across modules)
  • Nav contribution (the host renders the combined nav)

It's the substrate that codenanny is built on. But it's not codenanny-specific — use it for any modular Node app where you want clean module boundaries.

Install

npm install @codenanny/plugkit

Quickstart

import express from 'express';
import Database from 'better-sqlite3';
import { createHost, defineModule } from '@codenanny/plugkit';

const app = express();
const db = new Database('app.db');
const host = createHost({ app, db });

// Define a module
const greeter = defineModule({
  name: 'greeter',
  mountPath: '/hello',
  schema: {
    migrations: [
      `CREATE TABLE IF NOT EXISTS greetings(id INTEGER PRIMARY KEY, who TEXT, ts INTEGER)`,
    ],
  },
  router: ({ db, events }) => {
    const r = express.Router();
    r.get('/:who', (req, res) => {
      db.prepare('INSERT INTO greetings(who, ts) VALUES (?, ?)').run(req.params.who, Date.now());
      events.emit('greeted', { who: req.params.who });
      res.send(`hi, ${req.params.who}`);
    });
    return r;
  },
  nav: { id: 'greeter', label: 'Greeter', route: '/hello/world' },
  subscribe: {
    'module:registered': ({ name }) => console.log(`module ${name} joined the host`),
  },
});

host.register(greeter);

app.get('/nav', (req, res) => res.json(host.getNav(req.user)));
app.listen(3000);

Module shape

defineModule({
  name: 'string (required, unique)',
  mountPath: '/optional/custom/path',          // defaults to `/<name>`
  schema: { migrations: ['CREATE TABLE ...'] },// run inside a transaction on register
  router: ({ db, events, logger, host }) => Router,
  subscribe: { 'event:name': (payload) => {} },// host's event bus
  nav: { id, label, icon?, route, roles? } | [...]
});

Host shape

const host = createHost({ app, db, logger });

host.register(mod);                  // register a module
host.getNav(user);                   // filtered/ordered nav for a user
host.getModule(name);                // retrieve a registered module
host.events.on('greeted', handler);  // listen on the shared event bus
host.events.emit('whatever', data);  // emit on the shared event bus

Why this shape

  • Express router because everyone knows Express; no new framework to learn.
  • sqlite migrations because most small apps don't need anything more.
  • Event bus so modules can react to each other without import cycles.
  • Nav contribution so the host UI can render a coherent navrail without hardcoding what's where.

If you outgrow plugkit, you can replace it with anything that respects the same module shape.

License

MIT. Created by nobleglitch.