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

@procwire/client

v1.1.0

Published

Child-side client for Procwire IPC

Readme

@procwire/client

Child-side API for Procwire IPC.

Highlights

  • Client - Fluent builder for registering handlers
  • RequestContext - respond, ack, chunk, end, error
  • Event emission to parent process
  • Cancellation via ctx.aborted and ctx.onAbort()
  • Async response methods - backpressure-safe
  • ~2.5 GB/s throughput on named pipes

Installation

npm install @procwire/client

Requirements: Node.js >= 22

Dependencies: @procwire/protocol, @procwire/codecs

Quick Start

import { Client } from "@procwire/client";

const client = new Client()
  .handle("query", async (data, ctx) => {
    const results = await search(data);
    ctx.respond(results);
  })
  .handle("insert", async (data, ctx) => {
    ctx.ack({ accepted: true });
    await processInBackground(data);
  })
  .event("progress");

await client.start();

// Emit events to parent
client.emitEvent("progress", { percent: 50 });

API Reference

Client

Fluent builder for registering method handlers and events.

const client = new Client(options?)
  .handle(name, handler, definition?)
  .event(name, definition?)
  .start();

Constructor Options

interface ClientOptions {
  defaultCodec?: Codec; // Default codec for all methods/events
}

.handle(name, handler, definition?)

Register a method handler.

client.handle(
  "process",
  async (data, ctx) => {
    // Handle request and send response
    ctx.respond(result);
  },
  {
    response: "result", // "result" | "stream" | "ack" | "none"
    codec: msgpackCodec, // Optional, defaults to msgpack
    cancellable: true, // Support AbortSignal from parent
  },
);

.event(name, definition?)

Register an event that can be emitted to parent.

client.event("progress", { codec: msgpackCodec });

.start()

Start listening for requests from parent.

await client.start();
// Client is now ready to receive requests

.emitEvent(name, data)

Emit an event to the parent process.

client.emitEvent("progress", { percent: 75 });

RequestContext

Passed to method handlers to send responses back to parent.

interface RequestContext {
  readonly requestId: number; // For correlation
  readonly method: string; // Method being handled
  readonly aborted: boolean; // Was request aborted?

  onAbort(callback: () => void): void; // Abort callback

  respond(data: unknown): Promise<void>; // Full response
  ack(data?: unknown): Promise<void>; // Acknowledgment only
  chunk(data: unknown): Promise<void>; // Stream chunk
  end(): Promise<void>; // End stream
  error(err: Error | string): Promise<void>; // Error response
}

Important: All response methods are async to handle backpressure. Always await them.

Response Patterns

Single Response (result)

client.handle(
  "query",
  async (data, ctx) => {
    const result = await processQuery(data);
    await ctx.respond(result);
  },
  { response: "result" },
);

Streaming Response (stream)

client.handle(
  "generate",
  async (data, ctx) => {
    for (const item of generateItems(data)) {
      await ctx.chunk(item);
    }
    await ctx.end();
  },
  { response: "stream" },
);

Acknowledgment (ack)

client.handle(
  "enqueue",
  async (data, ctx) => {
    await ctx.ack({ queued: true, position: 42 });
    // Continue processing after acknowledgment
    await processInBackground(data);
  },
  { response: "ack" },
);

Fire-and-Forget (none)

client.handle(
  "log",
  (data, ctx) => {
    logger.info(data);
    // No response needed
  },
  { response: "none" },
);

Error Response

client.handle("validate", async (data, ctx) => {
  try {
    const result = validate(data);
    await ctx.respond(result);
  } catch (e) {
    await ctx.error(e);
  }
});

Cancellation

Handle request cancellation from parent.

client.handle(
  "longTask",
  async (data, ctx) => {
    const resources = await acquireResources();

    // Register cleanup on abort
    ctx.onAbort(() => {
      resources.release();
    });

    // Check abort status periodically
    for (const item of items) {
      if (ctx.aborted) {
        return; // Stop processing
      }
      await ctx.chunk(process(item));
    }

    await ctx.end();
  },
  { response: "stream", cancellable: true },
);

Error Handling

import { ProcwireClientError, ClientErrors } from "@procwire/client";

// Error factories
ClientErrors.methodNotFound("unknown"); // Unknown method called
ClientErrors.handlerError("process", err); // Handler threw error
ClientErrors.alreadyStarted(); // start() called twice

Architecture

┌─────────────────────────────────────────┐
│            Parent Process               │
│  ┌───────────────────────────────────┐  │
│  │   Module (uses @procwire/core)    │  │
│  │   - send(), stream(), onEvent()   │  │
│  └───────────────┬───────────────────┘  │
└──────────────────┼──────────────────────┘
                   │
    ┌──────────────┴──────────────┐
    │  Control: stdio (JSON-RPC)  │
    │  Data: named pipe (BINARY)  │
    └──────────────┬──────────────┘
                   │
┌──────────────────┼──────────────────────┐
│            Child Process                │
│  ┌───────────────┴───────────────────┐  │
│  │  Client (uses @procwire/client)   │  │
│  │  - handle(), event(), emitEvent() │  │
│  └───────────────────────────────────┘  │
└─────────────────────────────────────────┘

License

MIT