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

postal-transport-childprocess

v1.0.0

Published

child_process and cluster IPC transport for postal — bridges pub/sub across Node.js processes.

Readme

postal-transport-childprocess

child_process and cluster IPC transport for postal — bridges pub/sub across Node.js processes.

Installation

npm install postal postal-transport-childprocess

Usage

child_process

Parent:

import { fork } from "child_process";
import { addTransport, getChannel } from "postal";
import { connectToChild } from "postal-transport-childprocess";

const child = fork("./worker.js");
const transport = await connectToChild(child);
const remove = addTransport(transport);

// Clean up when the child exits
child.on("exit", () => remove());

Child (worker.js):

import { addTransport, getChannel } from "postal";
import { connectToParent } from "postal-transport-childprocess";

const transport = await connectToParent();
addTransport(transport);

cluster

Primary:

import cluster from "cluster";
import { addTransport } from "postal";
import { connectToClusterWorker } from "postal-transport-childprocess/cluster";

const worker = cluster.fork();
const transport = await connectToClusterWorker(worker);
const remove = addTransport(transport);

worker.on("exit", () => remove());

Worker:

import { addTransport } from "postal";
import { connectToClusterPrimary } from "postal-transport-childprocess/cluster";

const transport = await connectToClusterPrimary();
addTransport(transport);

API

connectToChild(child, options?)

Initiates a handshake from the parent to a forked child. Rejects if the child's IPC channel is closed or the handshake times out.

connectToParent(options?)

Waits for a SYN from the parent. Rejects immediately if the process has no IPC channel (not spawned with fork()).

connectToClusterWorker(worker, options?)

Same as connectToChild but accepts a cluster.Worker.

connectToClusterPrimary(options?)

Same as connectToParent but for cluster workers.

createIPCTransport(endpoint)

Low-level factory. Accepts any object with send(), on('message'), and removeListener('message'). Use this if you manage the handshake yourself.

Options

| Option | Type | Default | Description | | --------- | -------- | ------- | --------------------------------- | | timeout | number | 5000 | Handshake timeout in milliseconds |

Known Limitations

  • Binary payloads: Node IPC uses JSON serialization. Buffer and ArrayBuffer values are serialized as JSON objects — they arrive intact but as plain objects, not typed array instances. Base64-encode binary data before sending it across processes.
  • Reconnection: This transport does not attempt to reconnect if the IPC channel closes. Wire up child.on('exit') / process.on('disconnect') to dispose the transport and re-establish if needed.