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

koa-upgrade

v1.0.1

Published

koa-upgrade ===========

Readme

koa-upgrade

Allow koa to handle websockets like regular requests

  • use any middleware (including routers, compression, etc.) for normal & upgrade requests
  • upgrade to a websocket at any point in your app
  • auto close websockets at the end of the chain or in case of an uncaught error

how it works

Since node's http-server upgrade - event does not emit a response object as is the case for the request - event, koa-upgrade mimicks one that behaves exalty like a normal response object. This allows koa to handle the upgrade request like any other request & send a response just like always. So, in theory, any middleware should work the same for normal & upgrade requests.

The only difference to regular requests is, that you are able to upgrade them to a WebSocket at any point in your middleware chain. As soon as you have done that, writes to the responses body will be ignored, and you have to write to the websocket instead. Additionally, the websockets gets automatically closed when your request is done, or some uncaught errors occoured.

The cool thing is, that it's up to you if you want to threat an upgrade request like any other request, or if & when you want to upgrade to a WebSocket.

why not koa-websocket

The main problem with koa-websocket is, that you have 2 separate middleware chains for regular requests & upgrade requests. If you want to use a middleware in both chains, you have to do it twice. This can become pretty messy in large chains. So in contrast to koa-websocket, koa-upgrade does not threat upgrade requests completely different to regular requests. Instead, if you want a specific request to be handled differently, you'd have to do it manually in the middleware.

usage

First, install koa-upgrade to your app

var koa = require("koa");
var upgrade = require("koa-upgrade");

var app = koa();
upgrade(app);

From now on, you can call upgrade() on the context.

app.use(function*(){
	if(this.get("Connection") == "Upgrade"){
		var connection = yield this.upgrade();
		connection.send("Hello World!");
	}else{
		this.status = 400;
		this.body = "A upgrade request was expected";
	}
})