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

@browsercore/transport

v0.2.1

Published

Generic byte-stream transport abstraction (TCP sockets, DNS, backpressure). No knowledge of TLS or HTTP.

Downloads

1,080

Readme

@browsercore/transport

npm version coverage lint

@browsercore/transport abstracts socket management, DNS resolution, connection lifecycle, backpressure, and timeouts behind a small, strongly typed interface. It deliberately knows nothing about TLS, HTTP, QUIC, proxies, or browser fingerprinting, making it the foundation on which higher protocol layers are built. This package forms the lowest layer of the BrowserCore networking stack.

Install

npm install @browsercore/transport

Quick usage

import { connect } from "@browsercore/transport";

const transport = await connect({ host: "example.com", port: 443 });

await transport.write(handshakeBytes);
const chunk = await transport.read();

// Or stream via events:
transport.on("data", (chunk: Uint8Array) => { /* ... */ });
transport.on("state", (s) => { /* connecting -> open -> closing -> closed */ });

await transport.close();

Package Dependencies

@browsercore/transport
├── node:net
├── node:dns
└── node:events

This package has no runtime dependencies and imports no other @browsercore/* packages.

Position in BrowserCore

Application
      │
 HTTP/3 / HTTP/2 / HTTP/1
      │
      TLS
      │
@browsercore/transport
      │
     TCP
      │
      IP

Every higher networking layer communicates with the network exclusively through the Transport interface.

Documentation

Full API documentation (generated from TSDoc annotations): docs/README.md

Public API

| Export | Kind | Purpose | | --- | --- | --- | | connect() | function | Resolve DNS and establish a TCP transport | | resolveHost() | function | Resolve a host to an address (injectable lookup) | | TcpTransport | class | Concrete Transport implementation over node:net.Socket | | Transport | interface | Public contract higher layers depend on | | TransportOptions | interface | Options for connect() (timeouts, IPv6, DNS, no-delay) | | TransportState | discriminated union | connecting \| open \| closing \| closed | | CloseReason | discriminated union | Why a transport closed (client_close, remote_close, error, timeout) | | ResolvedAddress | interface | Address family + IP returned by resolveHost() | | TransportError | class | Base typed error (with details and cause) | | ConnectTimeoutError | class | Connection timed out | | DnsResolutionError | class | DNS lookup failed | | IdleTimeoutError | class | No data flowed within the idle timeout | | ReadTimeoutError | class | A read() saw no data within the per-read timeout |

Dependency graph

@browsercore/transport
  └─ node:net / node:dns / node:events

No other @browsercore/* packages are imported.

License

MIT