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

@the-link/ipc

v0.2.1

Published

Local process and socket IPC adapters for The Link.

Readme

The Link IPC

Local inter-process communication adapters for The Link.

Install

npm install @the-link/ipc

Process

ProcessLink adapts an existing Node.js process IPC channel. The channel may come from fork() or from spawn() with an ipc standard-I/O entry.

import { spawn } from "node:child_process"
import { ProcessLink } from "@the-link/ipc/process"

const child = spawn(process.execPath, ["worker.js"], {
    serialization: "advanced",
    stdio: ["inherit", "inherit", "inherit", "ipc"]
})

const link = new ProcessLink(child)

Inside the child, the current process is the default target:

import { ProcessLink } from "@the-link/ipc/process"

const link = new ProcessLink()

ProcessLink uses the serialization policy selected when the channel was created. It does not create, terminate, or disconnect the process.

Socket

The Socket adapters communicate through a Unix domain socket on POSIX systems or a named pipe on Windows.

import { SocketServer } from "@the-link/ipc/socket-server"

const server = new SocketServer(address)

server.onConnection(link => {
    link.$inbound.subscribe("sum", (left: number, right: number) => left + right)
})

await server.listen()
import { SocketClient } from "@the-link/ipc/socket-client"

const client = new SocketClient(address)

await client.connect()

const total = await client.$outbound.publishFirst<number>("sum", 20, 22)

await client.disconnect()

Socket publications are bidirectional and carry remote results and failures. UTF-8 JSON bytes are used by default. Applications may replace the Socket serialization policy through setSerialize() and setDeserialize().

POSIX sockets use mode 0600 by default. Applications remain responsible for selecting and managing their addresses.

Development

bun install --frozen-lockfile
bun run verify

License

MIT