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 🙏

© 2025 – Pkg Stats / Ryan Hefner

pevnt

v1.0.5

Published

Command runner and consumer

Readme

📨 pevnt

NPM Version License Downloads

A lightweight Command runner + Consumer for Node.js (TypeScript), supporting both Worker Threads and Child Processes.


📦 Installation

npm install pevnt

🚀 Quick Start

1. Create a Consumer

src/main.ts

import { MessageConsumerBase, TransportType } from "pevnt";

const itemConsumer = new MessageConsumerBase()
    .transport(TransportType.PROCESS) // or TransportType.WORKER
    .filename("./src/item-command.ts")
    .consumers(async ({ data }) => {
        console.log({ data });
        return { itemId: data.item_id };
    })
    .on("exit", async (id, { code, signal }) => {
        console.log("Item consumer on exit:", { id, code, signal });
    })
    .on("close", async (id, { code, signal }) => {
        console.log("Item consumer on close:", { id, code, signal });
    })
    .on("disconnect", async (id) => {
        console.log("Item consumer on disconnect:", {
            id,
        });
    });

// Run the consumer
const { id } = await itemConsumer.create({
    params: { itemId: 10 },
});

console.log({ exists: itemConsumer.exists(id) });

// Stop all running consumers later
for (const id of itemConsumer.listConsumers()) {
    await itemConsumer.stop(id);
}

2. Define the Command

src/item-command.ts

import { CommandRunner } from "pevnt";

export async function main() {
    await CommandRunner(async ({ params, sendEventAndReturn }) => {
        async function start({ itemid: item_id = 0 }) {
            const res = await sendEventAndReturn({
                data: { item_id },
            });
            console.log({ res });
        }

        await start(params);
    });
}

if (process.env.NODE_ENV !== "test") {
    main();
}

🔄 Flow

  1. Consumer (MessageConsumerBase) is created with a chosen transport (worker or process).
  2. A Command (item-command.ts) is registered with dynamic arguments.
  3. When executed, the CommandRunner communicates with the Consumer by sending/receiving messages.
  4. The .consumers() handler processes each incoming message.
  5. Consumers can later be listed with .listConsumers() and stopped with .stop(id).

📘 API Reference

MessageConsumerBase

  • .transport(type: TransportType) → defines transport (worker or process)

  • .filename(path) → registers filename

  • .consumers(handler) → handles incoming messages. (handler: Array of Class/Object or Function)

    Function:
    .consumers(async ({ data }) => {
        return { itemId: data.item_id };
    })
    Class/Object required methods: .getStatus() => "myStringId" .onMessage({ data }): Promise
class UserConsumerCompleted implements IStepMessage {
    public getStatus(): string {
        return "completed";
    }

    public async onMessage({ data }) {
        // code
    }
}
  • .create({ params }) → executes the command with given parameters
  • .listConsumers() → iterable of running consumer IDs
  • .stop(id) → stops a specific consumer
  • .exists(id) → check if it is running
  • .on("exit", async (id, { code, signal }) => void) → listen when executing "exit" event
  • .on("close", async (id, { code, signal }) => void) → listen when executing "close" event
  • .on("disconnect", async (id) => void) → listen when executing "disconnect" event (ipc)

CommandRunner

Runs a command file with access to:

  • params → parsed params from .create()
  • sendEventAndReturn(payload, type?: string) → sends a message back to the consumer and waits for response. (type: status id from .consumers(handler))

🌐 Transport Options

enum TransportType {
    WORKER = "WORKER",
    PROCESS = "PROCESS",
    MEMORY = "MEMORY",
}
  • WORKER → uses Worker Threads
  • PROCESS → uses Child Process
  • MEMORY → uses await import main()