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

drouter

v0.1.3

Published

A node.js directory-driven router for connect/express

Readme

drouter

A node.js directory-driven router for connect/express.

It does not use the router functionality of connect/express. The new version of connect(3.x)/express(4.x) should be compatible.

Usage

    var drouter = require("drouter"),
        express = require("express"),
        app = express(); // connect();
    
    
    drouter("directory_root", app, "some user defined data object");
    // return a list of path and middleware pairs 
    //    [{pt:"loaded path", mw:"loaded module"}, ...].
    // at this point, app has all the middleware loaded at their path
    // using "app.use(path, middlewareCreator(userData))"
    

Example

Suppose we have a directory structure as follow:

+mw1
    index.js
    +abc
        index.js
        +def
            index.js
            +fgh
               + hij
                    index.js
                +ijk
            +ghi
        +efg
    +bcd
        index.js
    +cde

Each index.js file exports a function which takes in a user defined data object and returns a connect/express compatible middleware. drouter("mw1", app, {msg:"some msg"}) will load the app at these paths :

/mw1
/mw1/abc
/mw1/abc/def
/mw1/bcd

The index.js under hij will not be loaded because its parent directory fgh is not loadable and thus all its children are ignored. Loadable condititon is applied by require.resolve("module").

Other

Suggestion and help are always welcome !

Licence

MIT