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

route-order

v0.1.0

Published

Sort common router patterns by specificity.

Downloads

1,079

Readme

route-sort

build status

Comparator to compare URI route patterns by specificity.

Useful for Express apps, for example, to make sure more specific route patterns are matched before more generic ones.

Acutally, currently only supports Express style routes. Could be expanded.

API

Where var routeOrder = require('route-order') routeOrder accepts the following configuration options:

  • order: May be 'nonascending' or 'na' or 'nondescending' or 'nd'
  • default: If supplied, the string to determine a catchall route, i.e. route with lowest priority. Defaults to an empty string.

Behaviour

  • Deeper routes are more specific, e.g. /base/id > /base
  • If two routes have the same depth, specificity is then determined by the position of its bound parts, i.e. the position of parts which don't have a free variable like /:id. The more and the deeper the bound parts, the more specific.

Usage

// Require returns a higher order function which accepts config and
// returns a comparator function
var routeOrder = require('route-order')

var routes = [
  '/',
  '/resource/:name',
  '/resource/doggy'
]

// Sorts in nonascending order by default
routes.sort(routeOrder())
// returns ['/resource/doggy', '/resource/:name', '/']

With Express:

var express = require('express')
var specificity = require('route-order')()
var app = express()

var views = {
  '/': IndexView,
  '/resource/doggy': DoggyView,
  '/resource/:name': ResourceView
}

Object.keys(views)
    .sort(specificity)
    .forEach(function(route) {
      app.use(route, views[route])
    })

License

MIT