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

@rcompat/net

v0.0.2

Published

Standard library TCP/Unix sockets

Readme

@rcompat/net

TCP and unix socket connections for JavaScript runtimes.

What is @rcompat/net?

A cross-runtime module for opening raw TCP and unix domain socket connections, backed by native Web Streams. Works consistently across Node, Deno, and Bun — each runtime uses its own native socket implementation under the hood (node:net, Bun.connect, Deno.connect), so there's no shared polyfill or compatibility shim sitting between you and the runtime.

Installation

npm install @rcompat/net
pnpm add @rcompat/net
yarn add @rcompat/net
bun add @rcompat/net

Usage

Opening a connection

import net from "@rcompat/net";

// unix domain socket
const socket = await net.open({ path: "/var/run/example.sock" });

// tcp
const socket = await net.open({ host: "127.0.0.1", port: 9999 });

Writing and reading

import net from "@rcompat/net";

const socket = await net.open({ path: "/var/run/example.sock" });

await socket.write("ping\n");
await socket.end(); // half-close — stop writing, keep reading

const response = await socket.text(); // drains readable to a string

Streaming chunks

import net from "@rcompat/net";

const socket = await net.open({ host: "127.0.0.1", port: 9999 });

await socket.write("subscribe\n");

for await (const chunk of socket) {
  console.log(new TextDecoder().decode(chunk));
}

Closing

import net from "@rcompat/net";

const socket = await net.open({ path: "/var/run/example.sock" });

await socket.write("hello\n");
await socket.close(); // closes both write and read sides

end() only closes the write side (sends FIN, server can still respond) — use it when you expect a response after writing. close() tears down both sides — use it when you're done with the connection entirely.

API Reference

net

function open(options: NetOptions): Promise<Socket>;

NetOptions

type TCPOptions = { host: string; port: number };
type UnixOptions = { path: string };
type NetOptions = TCPOptions | UnixOptions;

A plain discriminated union — pass { host, port } for TCP or { path } for a unix domain socket. No separate transport tag needed.

Socket

class Socket {
  readable: ReadableStream<Uint8Array>;
  writable: WritableStream<Uint8Array>;

  write(data: string | Uint8Array): Promise<void>;
  end(): Promise<void>;
  close(): Promise<void>;
  text(): Promise<string>;

  [Symbol.asyncIterator](): AsyncIterator<Uint8Array>;
}

Socket isn't constructed directly — instances only come from net.open(). The type is exported for annotating function parameters and return types.

Examples

Talking to a control-plane socket (e.g. HAProxy)

import net from "@rcompat/net";

async function command(input) {
  const socket = await net.open({ path: "/var/run/haproxy.sock" });
  await socket.write(`${input}\n`);
  await socket.end();
  return socket.text();
}

await command("show info");

Simple TCP request/response

import net from "@rcompat/net";

const socket = await net.open({ host: "api.internal", port: 8080 });
await socket.write("STATUS\n");
await socket.end();

console.log(await socket.text());

Cross-Runtime Compatibility

| Runtime | Supported | | ------- | --------- | | Node.js | ✓ | | Deno | ✓ | | Bun | ✓ |

No configuration required — @rcompat/net resolves the correct native implementation per runtime via package export conditions.

License

MIT

Contributing

See CONTRIBUTING.md in the repository root.