New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

@dmail/filesystem-matching

Package Overview
Dependencies
Maintainers
1
Versions
6
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@dmail/filesystem-matching

[![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

  • 1.5.0
  • latest
  • Source
  • npm
  • Socket score

Version published
Maintainers
1
Created
Source

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

FAQs

Package last updated on 27 Sep 2019

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc