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

add-ws-handler

v1.0.4

Published

add a very simple ws handler that mimics a middleware function

Readme

add-ws-handler

This adds a no-features websockets middleware handler to an app. It's intended for use with express, but technically I guess you can use it with anything? This module is really quite awkward and you will almost certainly be better off with an alternative.

Unfortunately, express-ws didn't work for my use case (due to the way we're setting up express, which is out of my control), and it's using ws@3 instead of ws@5, so!

usage

For a server,

const express = require('express');
const addWebsocketHandler = require('add-ws-handler');

const app = express();
const server = app.listen(0);
addWebsocketHandler({ app, server });

app.ws(
  '/path',
  (req, ws, next) => {
    ws.send('hi');
    next();
  },
  (req, ws, next) => ws.send('hello')
);

and from a client,

const WebSocket = require('ws');
const ws = new WebSocket(`ws://localhost:${server.address().port}/path`);
ws.on('message', console.log);

The addWebsocketHandler function takes an object with two required parameters and two optional parameters:

  • app: (required) the object to attach the ws function to.

  • server: (required) the server that will be accepting requests and in particular will be emitting an 'upgrade' event when the it receives a WebSocket request

  • prefix: (optional) if the router or app will be mounted on a prefix, it should be passed in here so that we can append it to the paths that are registered:

    addWebsocketHandler({ app, server, prefix: '/prefix' });
    app.ws('/path', ...);
    
    // the above would respond to /prefix/path, not /path
  • prototype: (optional) Express adds a bunch of stuff to the http.IncomingMessage prototype. To make the req object a little more familiar, you can pass a prototype and we'll set the prototype of the req object for you.

    const Express = require('express');
    addWebsocketHandler({ app, server, prototype: Express.request  });
    
    app.ws('/path', (req, ws, next) => {
      // req.header() is defined as in Express, even though
      // http.IncomingMessage doesn't have it on its own
    });