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

global-router

v0.1.2

Published

A router which can be used for a bit of everything

Downloads

9

Readme

global-router

The idea is to create a router, which should play well in all environments, both in a node, client and universal application.

Usage

To create add routes, use the Route.add method, with the as a string. * matches anything while :params becomes parameters. The second parameter can be anything. These will be returned as an array for all matched routes when resolving an URL

var Router = require('global-router').Router;

var router = new Router();
router.add('/user/*', 'route1');
router.add('/user/:id', 'route2');
router.add('/user/:id/*', 'route3');
router.add('/user/*/images', 'route4');
router.add('/user/:id/images', 'route5');
router.add('/user/:id/details', 'route6');

To find url matches resolve is called on the router instance, which will output all matched routes.

router.resolve('/user/1234/images');

will output

[
  {
    "state": {
      "params": {}
    },
    "result": "route1"
  },
  {
    "state": {
      "params": {
        "id": "1234"
      }
    },
    "result": "route3"
  },
  {
    "state": {
      "params": {}
    },
    "result": "route4"
  },
  {
    "state": {
      "params": {
        "id": "1234"
      }
    },
    "result": "route5"
  },
]

Processing responses

To change output, for instance to create a React tree from elements, a processResponse(current, previous) can be send to the router, which will loop through all routes, and feed the returned from previous call to the next call.

var router = new Router({
  processResponse: function(current, previous) {
    if (previous) {
      return React.cloneElement(current.result, null, previous);
    } else {
      return current.result;
    }
  }
});

router.add('/user/*', <User />);
router.add('/user/:id', <Details />);

Using router.resolve('/user/1234') in the example above would then result in

<User>
  <Details />
</User>