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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@parthar/express-ws

v1.0.0

Published

Express with Websockets

Downloads

2

Readme

Express Ws

Express with Websockets

Consider this as a drop-in replacement for ExpressJS with additional functionality to handle Websockets in familiar express-middelware style.

Installation

$ npm install @parthar/express-ws --save # the package

Usage

var expressWs = require("@parthar/express-ws");
var express = require("express");

// use like normal express-apps
var appWs = expressWs();
appWs.get("/hello", function (req, res, next) {
    res.send("hello world");
});

// mix both kinds of apps
var app = express();
app.get("/express", function (req, res, next) {
    res.send("plain express");
});
appWs.use(app);

// handle websockets upgrades in express-style
// use res.upgradeWs to accept the upgrade
app.get("/ws", function (req, res, next) {
    isAuthorized(req.headers.authorization, function (err, auth) {
        if (err) {
            return res.sendStatus(500);
        }
        if (!auth) {
            return res.sendStatus(401);
        }
        res.upgradeWs(function (ws) {
            ws.on("open", function () {
                // websocket opened
            });
            ws.on("close", function () {
                // websocket closed
            });
            ...
        });
    });
});

// listen on a port; similar to http.Server.listen()
appWs.listen(8080, callback);

// close when done; closes all opened websocket-connections
appWs.close(callback);

// http & ws servers are available as attributes: appWs.httpServer & appWs.wsServer
// can use these attributes for full functionality provided by respective entities

Notes

The Websocker-server is started in "noServer" mode. Also, "clientTracking" is enabled, which means that all websocket clients are available on the server via appWs.wsServer.clients attribute. Refer to Websockets for more details.