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 🙏

© 2026 – Pkg Stats / Ryan Hefner

compare-uri-specificity

v1.0.1

Published

Helper function to compare the specificity of two URIs, routes, or paths

Readme

compare-uri-specificity

A helper function to compare the specificity of URIs, routes, and paths. When used in an array sort function, more specific URIs will come earlier than less specific ones.

Installation

npm install compare-uri-specificity

Usage

import { compareUriSpecificity } from 'compare-uri-specificity';

// Different segment lengths
compareUriSpecificity('/foo/bar', '/foo');     // -1 (first is more specific)
compareUriSpecificity('/foo', '/foo/bar');     // 1 (first is less specific)
compareUriSpecificity('/a/b/c', '/x/y');       // -1 (first is more specific)

// Wildcards vs concrete paths
compareUriSpecificity('/foo/bar', '/foo/*');   // -1 (concrete path is more specific)
compareUriSpecificity('/foo/*', '/foo/bar');   // 1 (wildcard is less specific)

// Partial segment matches
compareUriSpecificity('/foo', '/food');        // 1 (shorter segment is less specific)
compareUriSpecificity('/food', '/foo');        // -1 (longer segment is more specific)

// Equal specificity
compareUriSpecificity('/foo/bar', '/foo/baz'); // 0 (equal specificity)
compareUriSpecificity('/foo/', '/foo');        // 0 (trailing slashes ignored)

// Using with Array.sort()
const uris = ['/foo', '/foo/bar', '/foo/*', '/food'];
uris.sort(compareUriSpecificity);
// Result: ['/foo/bar', '/food', '/foo', '/foo/*']

// Error handling
compareUriSpecificity('foo//bar', '/foo');     // throws Error: Invalid URI format
compareUriSpecificity('/foo', null);           // throws Error: URI must be a string