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

multimatcher

v2.1.0

Published

multimatcher ============

Downloads

8

Readme

multimatcher

Install

npm install multimatcher

News

Version 2 of multimatcher has breaking changes. There is now an options argument, and the default for matching basename was true, but is now false.

Usage

var Matcher = require("multimatcher");

var m = new Matcher(["*.js"]);

m.test("file.js"); //returns true

m.test("file.txt"); //returns false

The Match Array

The array passed to the Matcher constructor can be:

  • glob pattern
  • RegExp
  • String that matches the end of a path
var Matcher = require("multimatcher");

var m = new Matcher([
    //Only one of these needs to match.
    "*.js",     //glob
    /\.js$/,    //RegExp
    '.js']);    //End of file name string.

m.test("file.js"); //returns true

m.test("file.txt"); //returns false

The end of the string matcher can be .js, file.js, or le.js. As long as it's an end of a file name.

Longer names will be more precise.

Just In Case

The order of patterns checking is:

  1. RegExp
  2. glob pattern
  3. End of file name string

API

multimatcher(array, options) -> matcher

The first argument to multimatcher should be an array of regular expression, glob strings, or path names.

The options argument should be the same as minimatch, and will only be used to control glob patterns.

matcher.find(array)

Using patterns find all the file name strings that match.

var m = new Matcher(['*.js']);
//Will print ['one.js', 'two.js']
console.log(m.find('one.js', 'two.js', 'three.xml']));

matcher.index(name)

Find the index of name in patterns.

If the name string does not match a pattern then the returned value equals -1.

var m = new Matcher(['*.xml', '*.js']);
//Will print 1
console.log(m.index('file.js'));

matcher.indexes(name)

Find all the indexes of name in patterns.

If the name string does not match an empty array is returned.

If there are matches an array of indexes returned.

var m = new Matcher(['*.js', '*.xml', '*.js']);
//Will print [0, 2]
console.log(m.indexes('file.js'));
//Will print []
console.log(m.indexes("I don't match."));