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

@jixo/opendweb-config

v0.1.0

Published

opendweb local plugin helper — definePlugin wraps the declare/hook subprocess protocol (runtime-agnostic ESM)

Readme

@jixo/opendweb-config

definePlugin helper for writing opendweb local plugin files — it wraps the declare/hook subprocess protocol (--opendweb-declare / --opendweb-hook + JSON over stdin/stdout) so a plugin only declares { name, hooks }.

Runtime-agnostic: Deno, Bun, and Node can all host a plugin file; there are no node: dependencies at import time.

Usage

// opendweb.plugins/cf.ts  (local plugin file referenced from opendweb.config.toml)
#!/usr/bin/env -S deno run
import { definePlugin } from "npm:@jixo/opendweb-config";

export default definePlugin({
  name: "my-notify",
  hooks: {
    async "server.postReady"(ctx) {
      // ctx.options — plugin options from opendweb.config.toml
      // ctx.server  — resolved server config (public URLs, ...)
    },
  },
});

Under Node/Bun the same file works with a plain import { definePlugin } from "@jixo/opendweb-config"; — only the shebang and specifier style differ.

Protocol notes

  • Declaring: the host runs the file with --opendweb-declare; definePlugin prints the hook manifest as JSON and exits.
  • Hook calls: the host runs it with --opendweb-hook <name> and pipes the context JSON via stdin; the return value (or thrown error) is printed as JSON on stdout.
  • stdout is fully flushed before the process exits (large hook results are never truncated mid-JSON).

License: MIT OR Apache-2.0.