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

@gvibehacker/browser-socket-server

v0.1.3

Published

Server library to enable browser access to native TCP sockets

Readme

@gvibehacker/browser-socket-server

Node.js transport that bridges browser-socket clients to real TCP sockets. It accepts browser WebSocket connections, multiplexes streams over a single socket, and hands them to your Node runtime so you can connect to or host arbitrary TCP services on behalf of the browser.

Install

npm install @gvibehacker/browser-socket-server

Quick Start

import { Transport } from "@gvibehacker/browser-socket-server";
import { WebSocketServer } from "ws";
import net from "node:net";

const wss = new WebSocketServer({ port: 8080, perMessageDeflate: false });
const transport = new Transport(wss);

transport.on("connection", (connection) => {
  connection.on("connect", (socket, { address, port }) => {
    const upstream = net.connect(port, address);

    upstream.on("connect", () => {
      socket.ack({
        address: upstream.localAddress!,
        port: upstream.localPort!,
        family: upstream.localFamily!,
        remoteAddress: upstream.remoteAddress!,
        remotePort: upstream.remotePort!,
      });

      upstream.on("data", (chunk) => socket.write(chunk));
      socket.readable.pipeTo(
        new WritableStream({
          write(chunk) {
            upstream.write(Buffer.from(chunk));
          },
        })
      );
    });

    upstream.on("error", (err) => socket.destroy(err.message));
  });
});

transport.start();
console.log("Bridge listening on ws://localhost:8080");

API Highlights

  • Transport binds to an existing ws server and emits connection events per browser.
  • Connection surfaces connect and listen events to map browser flows onto real TCP sockets.
  • Socket objects expose Node-like methods (ack, write, end, destroy) plus WHATWG streams for piping.
  • Flow control is handled by the binary protocol (24-bit length frames with window updates) so you can focus on wiring TCP endpoints.

See the generated Server API docs for the full surface area.

Development

  • npm run build – bundle TypeScript with Rollup and emit d.ts files.
  • npm run dev – watch source files and rebuild incrementally.
  • npm run docs – regenerate the HTML reference under docs/.

Pair this package with @gvibehacker/browser-socket-client in the browser or the Cloudflare Worker bridge for edge deployments.