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

path-to-tree

v0.1.0

Published

high performance alternative for path-to-regexp to create routing lib

Downloads

3

Readme

Build Status

A tiny(3kb) foundation for building fast router via Radix Tree strategy , high-performance alternative for famous path-to-regexp

You can use it both in browser or Node.js.

Install

npm i path-to-tree

Usage


const ptt = require('path-to-tree');

const tree = ptt()

tree.add('/user/:id', 2);

const { param } = tree.find('/user/1')

/**
 * ==> {
 *  param: {
 *     id: "1" 
 * } ,
 * marker: 2
 * }
 * 
 * /

API

ptt( routeMap )

create tree instance

param

  • routeMap: route map to add

const tree = ptt({
    '/blog/:id': 'blog',
    '/user/:id': 'user'
})

as same as


const tree = ptt()

tree.add( '/blog/:id', 'blog')
tree.add( '/user/:id', 'user')

tree.add( route, marker [, option ])

add a route pattern

  • route: route string like /api/blog/:id
  • marker: route marker which will return by find
  • option: route config
    • strict: when false , trailing delimiter is optional. (default: true)
    • end: when false, only match the prefix of the URL (default: true)

const ptt = require('path-to-tree');

const tree = ptt();

tree.add('/blog/:id', function(param)=>{
    console.log(param)
})

tree.find( path )

  • return : a object container marker and param

let ret = tree.find('/blog/1');

ret.marker(ret.param) // => {id: "1"}



// marker === 

support param

  • named param: '/api/blog/:id
  • anonymous param: '/api/(hello|world)'
  • optional param: /api/name-:id?/api/name-(id|co)?
  • complex param: /blog/dada-((?:hello|nice)?-world)

Example

Simple Koa Router


const ptt = require('../') // === require('path-to-tree')

function router(cfg) {

    const tree = ptt(cfg);

    return async function (ctx, next) {
        const match = tree.find(ctx.path)
        if (match) {
            ctx.param = match.param;
            await match.marker(ctx, next)
        } else {
            await next();
        }
    }
}


const Koa = require('koa');
const app = new Koa();


app.use(
    router({
        '/blog/:id': (ctx, next) => {
            ctx.body ='blog ' + ctx.param.id
        },
        '/user/:id(\\d+)': (ctx, next) => {

            ctx.body ='user ' + ctx.param.id
        }
    })
)

app.listen(8002, ()=>{
    console.log('server start at 8002')
})

Benchmark

router based on path-to-regexp , described as O(n) Time Complexity ( n means route's length )

By contrast, router based on path-to-tree described as O(1) Time Complexity .(consider the deepth of path as constant)

In my computer (MacBook Pro 15: 2.2 GHz Intel Core i7、16 GB 1600 MHz DDR3) , the result of the benchmark show as below.

size of routes is 3000, 200x fast

path-to-tree x 215 ops/sec ±0.45% (77 runs sampled)
path-to-regexp x 1.04 ops/sec ±0.39% (7 runs sampled)
Fastest is path-to-tree