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

@dmail/filesystem-matching

v1.5.0

Published

[![npm package](https://img.shields.io/npm/v/@dmail/filesystem-matching.svg)](https://www.npmjs.com/package/@dmail/filesystem-matching) [![ci status](https://github.com/dmail/filesystem-matching/workflows/ci/badge.svg)](https://github.com/dmail/filesystem

Readme

Filesystem matching

npm package ci status codecov

Collect a subset of files inside a folder.

Example

npm install @dmail/filesystem-matching

With the following file structure:

root/
  src/
    file.js
  index.js
  package.json

Executing code below:

const { matchAllFileInsideFolder } = require(" @dmail/filesystem-matching")

const matchingFileResult = await matchAllFileInsideFolder({
  folderPath: __dirname,
  metaDescription: {
    "/**/*.js": {
      type: "js",
    },
    "/**/*.json": {
      type: "json",
    },
  },
  predicate: ({ type }) => extension === "js",
})
console.log(matchingFileResult.map(({ relativePath }) => relativePath))

logs:

["/index.js", "/src/file.js"]

matchAllFileInsideFolder

Async function returning the subset of files you want from a folder.

This function takes several option documented below.

folderPath option

path to the root folder possibly containing files.

This option is required. It is compatible with backslashes in case you're on windows.

metaDescription option

Object associating meta to path using patterns.

This option is required. Each key is a pattern. Each value is an object representing meta associated to this pattern. You can test how pattern matches a path in a dedicated page. — see pattern and pathname matching playground

For instance the following metaDescription

{
  "/**/*.js": {
    "type": "js"
  },
  "/**/*.json": {
    "type": "json"
  }
}

Associates { "type": "js" } to any file ending with .js inside 0 or more subfolder and { "type": "json" } to any file ending with .json inside 0 or more subfolder.

predicate(meta)

Function receiving meta associated to a given file. If it returns true, the file will be considered as matching.

This option is required.

For every file, all pattern matching the file path are collected. Then, all meta associated to matching patterns are composed into a single object passed to predicate.

It means the following metaDescription

{
  "/**/*": {
    "shared": 42
  },
  "/**/*.js": {
    "type": "js"
  }
}

Calls

predicate({ shared: 42, type: "js" })

for every file ending with .js inside your folder.

matchingFileOperation({ cancellationToken, relativePath, meta, lstat })

Async function called on every matching file.

This function can be used to perform operation on files as soon as they matches. Without this option you have to wait matchAllFileInsideFolder to get the list of matching files. matchingFileOperation return value is awaited and available in every matching file under the property operationResult.

If you don't pass this option, default value is:

const matchingFileOperation = () => null