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

ramrod

v1.0.0

Published

the router you'd write if you were writing a router

Downloads

14

Readme

Ramrod

Build
Status v1.0.0

An extremely minimal router. Seriously, it's pretty much just an EventEmitter (but that's a good thing.) It's the router you'd write if you were writing a router.

Usage

Add to your project with npm install ramrod --add and include it in your node app. It's meant to be used with the http module. Here's what it looks like in action:

var http = require('http');
var ramrod = require('ramrod');
var router = ramrod();

router.add('my/:route', function(req, res, param ){
  res.writeHead(200);
  res.end('Hello '+ param +'\n');
});

router.add('foo/:bar', function(req, res, param, querystring ){
  res.writeHead(200);
  res.end('Hello '+ param +'\n');
});

router.on('*', function(req, res){
  res.writeHead(200);
  res.end('All other urls go here :)\n');
});

http.createServer(function(req, res){
  router.dispatch(req, res);
}).listen(3000);

ramrod([routes])

Returns a Ramrod instance and takes an optional routes object as its only argument.

The routes object takes the form:

{
  'route/:param1/:param2': function( req, res, p1, p2 ){
    // route handler
  },

  'namedRegExpRoute': /^custom\/(reg|ex)/,

  'route/:param': null
}

Routes can be processed as route/handler pairs, named Regular Expression routes, or a route directive with a null value.

ramrod.add(route, [name], [callback])

Route strings can contain :params and *splats that are passed to the route's callback when matched.

Named routes can be useful for aliasing a complex route string. If the name is present, the route will be given that event name. E.g.:

router.add('foo/:bar', 'foo'); // router will emit a 'foo' event

If a funtion is passed as the last argument, it will be used as the handler for the route being added. The callback is always passed the http.ClientRequest and http.ClientResponse objects as its first 2 arguments.

router.on('foo', function( req, res ){ ... });

ramrod.get(route, [name], [callback])

Adds a route handler that will only be triggered when req.method === GET

ramrod.post(route, [name], [callback])

Adds a route handler that will only be triggered when req.method === POST

ramrod.put(route, [name], [callback])

Adds a route handler that will only be triggered when req.method === PUT

ramrod.del(route, [name], [callback])

Adds a route handler that will only be triggered when req.method === DELETE

ramrod.on(event, callback)

Inhereted from EventEmitter

Callbacks recieve all the same arguments as when attached with add.

ramrod.dispatch(request, response)

Processes a request and a response object, emitting the first matched route from the ramrod.routes object. A before event is emitted prior to matching against the route table. If no matching routes are found, the '*' event is emitted.