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 🙏

© 2025 – Pkg Stats / Ryan Hefner

match-files

v0.1.1

Published

Recursive file filtering utils

Readme

MatchFiles

Simple (recursive) file finder. Designed to find files (not directories). Has simple filtering functionality built in for filtering by file and directory.

Examples

/*Imagine this structure:

  lib/
    file.js
    other.md
    module/
      file.js
      other.js

*/

Simple no filtering

var MatchFiles = require('match-files');

//1st is path, 2nd is options, 3rd is callback
MatchFiles.find(__dirname + '/lib', {}, function(err, files){
  //following standard node conventions

  console.log(files);
  //will output (in absolute paths)
  //Paths are *not* sorted so they may not appear
  //in the order you expect
  //['lib/file.js', 'lib/other.md' 'lib/module/file.js', 'lib/module/other.js']
});

Filtering Options

var MatchFiles = require('match-files');

//You can filter by file and by directory.
//If a directory is filtered files and directories under the
//filtered directory will *not* be searched.

function matchJsFiles(path){
  //paths are relative to the 'basepath' which is the initial
  //path set or the .basepath option given
}

function excludeModuleDir(path){
  //Exclude all directories named module (and their children)
  return !path.match(/\/module/);
}

MatchFiles.find(__dirname + '/lib', {
  fileFilters: [matchJsFiles], //always an array of functions
  directoryFilters: [excludeModuleDir]
}, function(err, files){
  console.log(files);
  //['lib/file.js']
});

Options

Note: the object given for options will be modified. I use file filters to exclude certain file types and directory filters to exclude things like .svn or .git.

{
  //String used to create relative paths for filters
  basepath: (default the path used for find) ,

  //Default an empty array. Used for recursion you can
  //pass an array of files to use as a base.
  files: [],

  //An array of functions that must return true for the 
  //file to be included in the results. Recieves a path relative to
  //base root as an argument.
  fileFilters: null,

  //An array of functions that must return true for the 
  //file to be included in the results. Recieves a path relative to
  //base root as an argument.
  directoryFilters: null

}

License

See LICENSE (MIT)