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

@fasteroid/partial-pattern-tree

v2.0.2

Published

Not quite partial regex matching, but pretty darn close!

Readme

@fasteroid/partial-pattern-tree

“Not quite partial regex matching, but pretty darn close!”

Premise

Say you want to assign "names" to a series of values and then search for them.

The "best" result—since users are creative and unpredictable—is to look for partial matches.  This is really easy if your "names" are just unchanging string literals (just see if they contain the search query), but becomes an absolute head-scratcher when you decide you want to name your list entry Order ID\d+ where \d+ is any sequence of digits.

And no, you can't just naively regex this either, because doing that forfeits partial matching.  "Order" (or just "der" if your user is a lunatic) doesn't match Order ID\d+, so the option won't show up 😭

So are you just cooked, or is there a way?  Fear not, as this package (kind of) solves your problem!

Usage

import { PartialPatternTree } from "@fasteroid/partial-pattern-tree"

type Pet = {
  importance: string,
  name: string
}

const tree = new PartialPatternTree<Pet>(
    [
        ["parake", /^e+/m, "t"], // this "name" matches parakeet, parakeeet, parakeeeee... you get the idea.
        {
            name: "Newton"
            importance: "actually ate my homework once (not kidding)"
        }
    ],
    [
        ["parrot"], // this name just looks for "parrot"
        {
            name: "Polly"
            importance: "has a crippling cracker addiction"
        }
    ]
)

tree.search("keeeeeeeeeee"); // returns an array containing Newton

But what if..?

  • Q: I want to order the search results based on relevance and I want it to not be complete garbage!
    • A: First of all that's not a question—but yes it does do that.  The metric I chose is "how many characters into the name must we skip to find the search query?"
  • Q: This is literally just a generalized suffix tree with extra steps!
    • Also not a question.  But good observation!
  • Q: If this is a suffix tree why aren't you constructing it with Ukkonen's algorithm?
  • Q: Why is this README so GOOFY?
    • A: To make you smile! Duh!!!

License

MIT License