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

rooter-router

v0.2.4

Published

Simple JavaScript Router

Downloads

8

Readme

rooter-router

This is a basic javascript router implementation. It doesn't do regex, and it is strongly biased toward specificity - routes are matched to their most specific equivalent.

It handles multiple levels of resources and dynamic segments, and can handle method-specific routes.

NOTE: If you elect to use method specific routes, you cannot also use general routes for that endpoint.

Splats: Rooter-router has a basic splats implementation. Note that splats are always treated as less specific, which has the following repercussions:

Given:

testRouter.add('/public/*', function (req, res, helper) {
      res.end(helper.routeMatched)
    })
  .add('/public/resource/:test', function (req, res, helper) {
      res.end(helper.dynamics.test)
    })

the test:

request(app)
      .get('/public/resource/foobar')
      .expect('foobar’)

passes. In addition, a less specific splat will not overrule a more specific splat. Hence:

testRouter.add('/public/*', function (req, res, helper) {
      res.end(helper.routeMatched)
    })
  .add('/public/special/*', function (req, res, helper) {
      res.end(helper.routeMatched)
    })

with a test of:

request(app)
      .get('/public/special/foo/bar/baz')
      .expect('/public/special/*’)

will also pass. Note that the route definitions above use method chaining, which is supported when adding routes.

Usage looks something like this:

var http = require('http'),
Rooter = require('rooter-router')

router = new Rooter

router.add('/foo', function(req, res, url){
    res.end('Index for ' + url.resources[0])
})
router.add('/foo/:id', function(req, res, url){
  res.end('Got an instance of a foo: ' + url.dynamics.id)
})
router.add('/foo/new', function(req, res, url){
  res.end('This must have been a get request')
},'GET')
router.add('/foo/:bar/baz', function(req, res, url){
  res.end( url.resources[0] + '/' + url.dynamics.bar + '/' + url.resources[1])
})

http.createServer(function (req, res) {
  router.handle(req, res)
}).listen(9001)

Note that the URL object available to your callback includes a standard url.parse object, in addition to elements such as:

  • resources (an array)
  • dynamics (an object, where the key name is the dynamic segment)
  • verb (method)
  • matchedRoute

However, resources and dynamics are not presently generated for splats.

Testing (jasmine) requires supertest (for testing only). Tests cover essential functions, and are visible at specs/rooterSpec.js