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

@jnode/websocket

v1.0.1

Published

Simple WebSocket package for Node.js.

Readme

@jnode/websocket

Simple WebSocket package for Node.js.

Installation

npm i @jnode/websocket

Quick start

Import

const { WSConnection, calculateWSKey } = require('@jnode/websocket');

Usage with @jnode/server

You can perform a WebSocket handshake within a custom handler:

const { WSConnection, calculateWSKey } = require('@jnode/websocket');

const wsHandler = (ctx) => {
  const key = ctx.headers['sec-websocket-key'];
  if (!key) throw 400;

  // Handshake
  ctx.res.writeHead(101, {
    'Upgrade': 'websocket',
    'Connection': 'Upgrade',
    'Sec-WebSocket-Accept': calculateWSKey(key)
  });
  ctx.res.detachSocket(); // Take control of the socket

  const ws = new WSConnection(ctx.req.socket, ctx.req.socket, {
      useMask: false // Servers should not mask frames sent to clients
  });

  ws.on('message', (msg) => {
    console.log('Received:', msg.payload);
    ws.send(0x1, 'Hello from server!'); // 0x1 is Text frame
  });

  ws.on('close', (code, reason) => {
    console.log(`Closed: ${code} ${reason}`);
  });
};

Reference

Class: WSConnection

The core class for managing a WebSocket connection over any duplex stream.

new WSConnection(readable, writable, options)

  • readable <stream.Readable> The input stream (e.g., a TCP socket).
  • writable <stream.Writable> The output stream.
  • options <Object>
    • maxMessageSize <number> The maximum allowed size for a single message. Default: 1048576 (1MB).
    • useMask <boolean> Whether to mask outgoing frames. Note: Servers MUST NOT mask frames sent to clients, while clients MUST mask frames sent to servers. Default: undefined (treated as false).
    • autoPing <boolean> Whether to automatically reply with a Pong frame when a Ping is received. Default: undefined.

ws.send(opcode, payload)

Sends a single WebSocket frame with fin bit set to 1.

ws.sendFrame(fin, opcode, payload)

Low-level method to send a raw WebSocket frame. Useful for manual fragmentation.

ws.close([code[, reason]])

  • code <number> Status code for closure. Default: 1000.
  • reason <string> Human-readable reason for closure.

Sends a Close frame and destroys the underlying writable stream.

Event: 'message'

  • message <Object>
    • opcode <number> 0x1 (text) or 0x2 (binary).
    • payload <string> | <Buffer> The message content. If opcode is 0x1, it is automatically converted to a string.

Emitted when a full message (including fragmented ones) is received.

Event: 'close'

Emitted when the connection is closed.

Event: 'ping' / 'pong'

Emitted when a Ping or Pong frame is received.


calculateWSKey(key)

  • key <string> The Sec-WebSocket-Key header from the client request.
  • Returns: <string> The base64 encoded SHA-1 hash required for the Sec-WebSocket-Accept header.

A helper function to facilitate the WebSocket handshake process.