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

@gvibehacker/browser-socket-cloudflare-worker

v0.1.3

Published

Cloudflare worker library to enable browser access to native TCP sockets

Downloads

6

Readme

@gvibehacker/browser-socket-cloudflare-worker

Cloudflare Workers transport for browser-socket. It terminates WebSocket connections from browsers, multiplexes every TCP stream, and proxies them through Cloudflare's connect() API so you can expose TCP services from the edge.

Install

npm install @gvibehacker/browser-socket-cloudflare-worker

Add it to an existing Wrangler project or scaffold a new worker and import the connection handler in your src/index.ts.

Worker Setup

import { Connection } from "@gvibehacker/browser-socket-cloudflare-worker";

export default {
  async fetch(request) {
    if (request.headers.get("Upgrade") !== "websocket") {
      return new Response("browser-socket worker", { status: 200 });
    }

    const pair = new WebSocketPair();
    const [client, server] = Object.values(pair);
    const connection = new Connection(server);

    connection.addEventListener("connect", async (event) => {
      const [socket, { host, port }] = event.detail;
      const tcp = connect({ hostname: host, port });

      socket.ack({ address: host, port, family: "IPv4", remoteAddress: "0.0.0.0", remotePort: 0 });
      socket.readable.pipeTo(tcp.writable).catch(() => socket.destroy("tcp write error"));
      tcp.readable.pipeTo(socket.writable).catch(() => socket.destroy("tcp read error"));
    });

    return new Response(null, { status: 101, webSocket: client });
  },
};

Deploy with Wrangler and point your browser client at the worker URL:

npm run build
npm run deploy

API Highlights

  • Connection wraps a worker-side WebSocket and emits DOM-style events (connect, listen, close).
  • Socket instances expose either WHATWG streams or helper methods (ack, write, destroy) to coordinate TCP flow control.
  • Protocol helpers (encodeFrame, parseSynPayload, frame constants) are exported for advanced integrations or tooling.

See the generated Cloudflare Worker API docs for all types and event signatures.

Development

  • npm run build – bundle TypeScript for worker deployment.
  • npm run dev / npm run start – run the worker locally with Wrangler.
  • npm run docs – rebuild the Typedoc reference.

Combine this transport with @gvibehacker/browser-socket-client in the browser and, optionally, the Node bridge for hybrid routing.