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

@nexpress/plugin-sdk

v0.3.6

Published

Plugin SDK for NexPress (definePlugin).

Readme

@nexpress/plugin-sdk

Plugin SDK for NexPress — the Next.js-based CMS. Author plugins with definePlugin().

Install

pnpm add @nexpress/plugin-sdk

Plugin model (v1)

Plugins are npm-package + rebuild, not hot-loadable. A plugin can register hooks, actions, routes, and scheduled tasks at startup. It cannot add collections or fields at runtime — those require schema codegen + a DB migration. Plugins run in-process with full Node access; there is no sandbox in v1.

Quick example

import { definePlugin } from "@nexpress/plugin-sdk";

export default definePlugin({
  manifest: {
    id: "reading-time",
    name: "Reading Time",
    version: "0.1.0",
  },
  hooks: {
    "content:beforeSave": async ({ doc, ctx }) => {
      if (typeof doc.body === "string") {
        const words = doc.body.split(/\s+/).length;
        doc.readingMinutes = Math.max(1, Math.round(words / 220));
      }
      return doc;
    },
  },
});

Then in your nexpress.config.ts:

import readingTime from "@nexpress/plugin-reading-time";

export default defineConfig({
  // ...
  plugins: [readingTime()],
});

Restart the server — the hook fires on every content:beforeSave.

Available extension points

  • hookscontent:beforeSave, content:afterSave, content:beforeDelete, content:afterDelete, member:*, media:*
  • actions — custom API handlers at /api/plugins/<id>/actions/<name>
  • routes — full route handlers at /api/plugins/<id>/<...path> (rate-limited at the framework level — see AGENTS.md)
  • scheduled — cron-style tasks dispatched by pg-boss

Links

License

MIT