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

@parisholley/road-runner

v1.1.8

Published

The fastest path resolver for URL routing on modern Node.JS

Downloads

3

Readme

Road Runner Router

travis dependencies version coverage size supported

A router for when latency is Wile E. Coyote :) Inspired by julienschmidt/httprouter and partly derived from
steambap/koa-tree-router.

Why is it fast?

chart

  • Params are detected and provided as objects, but no regex or value casting, strings only
  • Case sensitive (use .toLowerCase() when inserting/retrieving if you want case-insensitivity)
  • Limited validation (assuming you are going to pass in valid paths and HTTP methods)
  • No URL parsing, most environments provide some type of req.path functionality

Getting Started

The following snippet is the basic setup of the router, remember, it is up to you to tie into your favorite HTTP library and execute the handler code and return a response (if any):

import {RoadRunner} from "@parisholley/road-runner";

const router = RoadRunner();

router.addRoute('GET', '/path', () => {});

// handler === {value: "() => {}", params: {}}
const result = router.lookupRoute('GET', '/path');

result.value();

router.addRoute('GET', '/path/:nested', () => {});

// handler === {value: "() => {}", params: {nested: 'foobar'}}
const result2 = router.lookupRoute('GET', '/path/foobar');

result2.value();

Supported Path Syntax

  • /foo
  • /:foo
  • /*
  • /foo/:bar
  • /foo/*
  • /foo/:bar/baz
  • /foo/*/baz
  • /foo/:bar/baz/:bum
  • /foo/*/baz/*
  • /foo/:bar/baz/*
  • /foo/*/baz/:bum

Unsupported Path Syntax

  • /foo/:bar-:baz
  • /foo/bar:baz
  • /foo/bar-*

API Versioning

This library categorizes paths into buckets, which ultimately are up to you to decide the format of. Most developers will likely pass in the HTTP Method when adding routes, but you can choose any string value you would like. In the case of switching behavior based on an API version provided in the header, you could do something like this:

import {RoadRunner} from "@parisholley/road-runner";

const router = RoadRunner();

router.addRoute(`POST:2.1`, '/document/:id', () => {});

function doLookup(headers:Record<string,string>){
  const result = router.lookupRoute(`POST:${headers['version']}`, '/document/:id');
  
  result.value();
}