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

@zimtsui/koa-ws-filter

v0.0.5

Published

[![Npm package version](https://badgen.net/npm/v/@zimtsui/koa-ws-filter)](https://www.npmjs.com/package/@zimtsui/koa-ws-filter)

Downloads

14

Readme

koa-ws-filter

Npm package version

This middleware is intended to separate websocket upgrade request and normal http request for Koa 2.

Comparison

Why not @kudos/koa-websocket?

Beacause it is not a standard koa middleware. It polyfills the Koa object instead, breaking the encapsulation of Koa.

Why not @b3nsn0w/koa-easy-ws

Because a user middleware needs a conditional clause to predicate whether a connection is websocket. It's not graceful.

The graceful way is demonstrated by @koajs/router. See the usage below.

Usage

The grammar is similar to @koajs/router

-   koaRouter.<method>(<path>, <user-middleware>);
+   koaWsfilter.<protocol>(<user-middleware>);

-   koaRouter.routes()
+   koaWsFilter.protocols()

Examples

import WebSocket from 'ws';
import Koa from 'koa';
import Router from '@koa/router';

const filter = new KoaWsFilter();

const httpRouter = new Router();
httpRouter.get('/hello', async (ctx, next) => {
    ctx.body = 'hello';
    await next();
});
filter.http(httpRouter.routes());

const wsRouter = new Router();
wsRouter.all('/echo', async (ctx, next) => {
    // accept the websocket upgrade request
    const ws: WebSocket = await ctx.upgrade();
    await next();

    // echo
    ws.on('message', message => ws.send(message));
});
filter.ws(wsRouter.routes());

const koa = new Koa();
koa.use(filter.protocols());
koa.listen(3000);