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

@beyond-js/ipc

v1.0.10

Published

The IPC module enables structured communication between processes in a Node.js application, including:

Downloads

40

Readme

IPC Module

The IPC module enables structured communication between processes in a Node.js application, including:

  • Main process ↔ Child process communication (both directions).
  • Child ↔ Child communication, routed through the main process.

The main process is referred to as "main", and it acts as the central coordinator for message routing. Child processes communicate with each other and with the main process through a unified API, allowing:

  • Remote action execution (similar to RPC).
  • Event-based communication (publish-subscribe).

The system automatically handles message routing, ensuring that:

  • Child processes can send actions or events to other children (via the main process).
  • The main process can directly interact with any child.
  • Communication is asynchronous, with promise-based action resolution.

This module simplifies inter-process messaging and abstracts away the complexity of managing forks, message serialization, and routing logic.


Installation

npm install @beyond-js/ipc

Usage

The unified module automatically detects if it's running in the main or a child process, so a single import is all that's needed for most contexts.

import { ipc } from '@beyond-js/ipc/wrapper';

Alternatively, you can manually import the main or child handler if you prefer to manage them explicitly.

import { ipc } from '@beyond-js/ipc/main';
import { ipc } from '@beyond-js/ipc/child';

API

The IPC interface exposes a unified API for both main and child processes.
The same methods are available in all contexts; behavior is handled internally based on the process type.

Register a Child Process (main only)

const child = fork('./child.js');
ipc.register('child-a', child);

Handle Actions

ipc.handle('get-time', () => new Date().toISOString());

Execute Actions

const time = await ipc.exec('child-a', 'get-time');

Emit and Subscribe to Events

ipc.on('child-a', 'status', data => {
	console.log('Status from child-a:', data);
});
ipc.emit('status', { ready: true });

Unregister a Child

ipc.unregister('child-a');

Remove Action Handlers

ipc.unhandle('get-time');

License

MIT