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

wild2wild_matcher

v0.5.4

Published

Compare two wildcard strings to each other

Downloads

8

Readme

wild2wild_matcher

A function to match two wildcard strings to each other. Supported wild cards: * - Zero or more characters ? - Exactly one character

This is actually a subset of a regular expression partial match. Both of which are not available OOB in JS.

A use case example:

When only part of the input is available and there is a need to understand whether this input may potentially be completed to match a desired pattern (described with wildcards) in order to show a notification to the user. Appending the partial input with * and matching it with the desired pattern will reveal if the input can be completed to match the pattern.

Examples:

const {w2match} = require('wild2wild_matcher');

console.log(w2match('hello\*world', 'hello\*'));           // => true
console.log(w2match('hello\*world', 'hello\*jimbo'));      // => false
console.log(w2match('h?llo?wor?d', '??llo w?rld'));        // => true
console.log(w2match('he??o?world', 'he\*d'));              // => true
console.log(w2match('he??o?world', 'helo world\*'));       // => false

Efficiency

This recursive algorithm is not the most efficient one. A more efficient (but less elegant) algorithm can be written by separating to several cases. For example, noticing that if there is at least one * in the middle of each string, there is only a need to compare the prefixes (before the first *s) and the suffixes (after the last *s). Another case is when only one string has *s in the middle. Then there is a need to check each substring delimited by *s for containment in the other string and also check the order. Other cases include when the *s are in the beginning and end of the strings.