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

rx-request-handler

v0.2.1

Published

An Rx based http request handler with simple middleware

Readme

Rx Request Handler

This is an Rx request handler meant to work with the rx-router module. This version leverages a middleware format that was inspired by Clojure's ring specification.

The previous middleware implementation was effectively a modeling of unix pipes done with Rx. This version of middleware still leverages Rx but it lets you model a flow similar to a call stack. To visualize the difference check out the following ascii scribbles.

Previous pipe based middleware implementation:

     Request
        |
        V
------------------      --------------     -------------------
| Authentication | - -\ | Controller | --\ |     Caching     |
| pre-middleware | - -/ |   action   | --/ | post-middleware |
------------------      --------------     -------------------
                                                    |
                                                    V
                                                 Response

Current ring spec based middleware implementation:

     Request
        |
        V
------------------     --------------     --------------
| Authentication | --> |  Caching   | --> | Controller |
|   middleware   | <-- | middleware | <-- |   action   |
------------------     --------------     --------------
        |
        V
     Response

The previous implementation forced every middleware to choose whether it was a pre-action or post-action middleware. This creates nasty state passing situations in the cases where you need to coordinate between a pre-action and post-action middleware.

The new ring spec based implementations allows each middleware to choose whether it wants to be a pre-action, post-action middleware or even both. This enables the middleware to fully encapsulate all of it's state and gets rid of the need to attach middleware specific state to the data object flowing through the request cycle.

Example

var Rx           = require("rx");
var RxHttpServer = require("rx-http-server");
var router       = require("rx-router");
var handler      = require("rx-request-handler");

var defaultHandler = handler(function(data) {
    data.result = "no match found";
    return Rx.Observable.fromArray([data]);
});

var preAction = function(next) {
    return function(data) {
        data.result = "[pre] ";
        return Rx.Observable.returnValue(data).flatMap(next);
    };
};

var postAction = function(next) {
    return function(data) {
        return next(data).map(function(n) {
            n.result += " [post]"
            return n;
        });
    };
};

var rootHandler = handler({

    middleware: [
        preAction,
        postAction
    ],

    action: function(data) {
        data.result += "hello";
        return Rx.Observable.fromArray([data]);
    }

});

var regexHandler = handler(function(data) {
    data.result = "hello from regex";
    return Rx.Observable.fromArray([data]);
});

var server = new RxHttpServer();
var routes = router(defaultHandler, {
    "GET": [
        ["/",           rootHandler],
        [/^\/test\/.+/, regexHandler]
    ]
});

server.requests.flatMap(routes).subscribe(function(data) {
    data.response.writeHead(200, {"Content-Type": "text/plain"});
    data.response.end(data.result);
});

server.listen(3000);