Git Product home page Git Product logo

micromatch / micromatch Goto Github PK

View Code? Open in Web Editor NEW
2.6K 24.0 138.0 1.14 MB

Highly optimized wildcard and glob matching library. Faster, drop-in replacement to minimatch and multimatch. Used by square, webpack, babel core, yarn, jest, ract-native, taro, bulma, browser-sync, stylelint, nyc, ava, and many others! Follow micromatch's author: https://github.com/jonschlinkert

Home Page: https://github.com/micromatch

License: MIT License

JavaScript 100.00%
glob glob-pattern glob-matching matcher bash javascript multimatch minimatch regex regular-expression

micromatch's Introduction

micromatch NPM version NPM monthly downloads NPM total downloads Tests

Glob matching for javascript/node.js. A replacement and faster alternative to minimatch and multimatch.

Please consider following this project's author, Jon Schlinkert, and consider starring the project to show your ❤️ and support.

Table of Contents

Details

Install

Install with npm (requires Node.js >=8.6):

$ npm install --save micromatch

Sponsors

Become a Sponsor to add your logo to this README, or any of my other projects


Quickstart

const micromatch = require('micromatch');
// micromatch(list, patterns[, options]);

The main export takes a list of strings and one or more glob patterns:

console.log(micromatch(['foo', 'bar', 'baz', 'qux'], ['f*', 'b*'])) //=> ['foo', 'bar', 'baz']
console.log(micromatch(['foo', 'bar', 'baz', 'qux'], ['*', '!b*'])) //=> ['foo', 'qux']

Use .isMatch() to for boolean matching:

console.log(micromatch.isMatch('foo', 'f*')) //=> true
console.log(micromatch.isMatch('foo', ['b*', 'f*'])) //=> true

Switching from minimatch and multimatch is easy!


Why use micromatch?

micromatch is a replacement for minimatch and multimatch

  • Supports all of the same matching features as minimatch and multimatch
  • More complete support for the Bash 4.3 specification than minimatch and multimatch. Micromatch passes all of the spec tests from bash, including some that bash still fails.
  • Fast & Performant - Loads in about 5ms and performs fast matches.
  • Glob matching - Using wildcards (* and ?), globstars (**) for nested directories
  • Advanced globbing - Supports extglobs, braces, and POSIX brackets, and support for escaping special characters with \ or quotes.
  • Accurate - Covers more scenarios than minimatch
  • Well tested - More than 5,000 test assertions
  • Windows support - More reliable windows support than minimatch and multimatch.
  • Safe{#braces-is-safe} - Micromatch is not subject to DoS with brace patterns like minimatch and multimatch.

Matching features

  • Support for multiple glob patterns (no need for wrappers like multimatch)
  • Wildcards (**, *.js)
  • Negation ('!a/*.js', '*!(b).js')
  • extglobs (+(x|y), !(a|b))
  • POSIX character classes ([[:alpha:][:digit:]])
  • brace expansion (foo/{1..5}.md, bar/{a,b,c}.js)
  • regex character classes (foo-[1-5].js)
  • regex logical "or" (foo/(abc|xyz).js)

You can mix and match these features to create whatever patterns you need!

Switching to micromatch

(There is one notable difference between micromatch and minimatch in regards to how backslashes are handled. See the notes about backslashes for more information.)

From minimatch

Use micromatch.isMatch() instead of minimatch():

console.log(micromatch.isMatch('foo', 'b*')); //=> false

Use micromatch.match() instead of minimatch.match():

console.log(micromatch.match(['foo', 'bar'], 'b*')); //=> 'bar'

From multimatch

Same signature:

console.log(micromatch(['foo', 'bar', 'baz'], ['f*', '*z'])); //=> ['foo', 'baz']

API

Params

  • list {String|Array}: List of strings to match.
  • patterns {String|Array}: One or more glob patterns to use for matching.
  • options {Object}: See available options
  • returns {Array}: Returns an array of matches

Example

const mm = require('micromatch');
// mm(list, patterns[, options]);

console.log(mm(['a.js', 'a.txt'], ['*.js']));
//=> [ 'a.js' ]

Returns a matcher function from the given glob pattern and options. The returned function takes a string to match as its only argument and returns true if the string is a match.

Params

  • pattern {String}: Glob pattern
  • options {Object}
  • returns {Function}: Returns a matcher function.

Example

const mm = require('micromatch');
// mm.matcher(pattern[, options]);

const isMatch = mm.matcher('*.!(*a)');
console.log(isMatch('a.a')); //=> false
console.log(isMatch('a.b')); //=> true

Returns true if any of the given glob patterns match the specified string.

Params

  • str {String}: The string to test.
  • patterns {String|Array}: One or more glob patterns to use for matching.
  • [options] {Object}: See available options.
  • returns {Boolean}: Returns true if any patterns match str

Example

const mm = require('micromatch');
// mm.isMatch(string, patterns[, options]);

console.log(mm.isMatch('a.a', ['b.*', '*.a'])); //=> true
console.log(mm.isMatch('a.a', 'b.*')); //=> false

Returns a list of strings that do not match any of the given patterns.

Params

  • list {Array}: Array of strings to match.
  • patterns {String|Array}: One or more glob pattern to use for matching.
  • options {Object}: See available options for changing how matches are performed
  • returns {Array}: Returns an array of strings that do not match the given patterns.

Example

const mm = require('micromatch');
// mm.not(list, patterns[, options]);

console.log(mm.not(['a.a', 'b.b', 'c.c'], '*.a'));
//=> ['b.b', 'c.c']

Returns true if the given string contains the given pattern. Similar to .isMatch but the pattern can match any part of the string.

Params

  • str {String}: The string to match.
  • patterns {String|Array}: Glob pattern to use for matching.
  • options {Object}: See available options for changing how matches are performed
  • returns {Boolean}: Returns true if any of the patterns matches any part of str.

Example

var mm = require('micromatch');
// mm.contains(string, pattern[, options]);

console.log(mm.contains('aa/bb/cc', '*b'));
//=> true
console.log(mm.contains('aa/bb/cc', '*d'));
//=> false

Filter the keys of the given object with the given glob pattern and options. Does not attempt to match nested keys. If you need this feature, use glob-object instead.

Params

  • object {Object}: The object with keys to filter.
  • patterns {String|Array}: One or more glob patterns to use for matching.
  • options {Object}: See available options for changing how matches are performed
  • returns {Object}: Returns an object with only keys that match the given patterns.

Example

const mm = require('micromatch');
// mm.matchKeys(object, patterns[, options]);

const obj = { aa: 'a', ab: 'b', ac: 'c' };
console.log(mm.matchKeys(obj, '*b'));
//=> { ab: 'b' }

Returns true if some of the strings in the given list match any of the given glob patterns.

Params

  • list {String|Array}: The string or array of strings to test. Returns as soon as the first match is found.
  • patterns {String|Array}: One or more glob patterns to use for matching.
  • options {Object}: See available options for changing how matches are performed
  • returns {Boolean}: Returns true if any patterns matches any of the strings in list

Example

const mm = require('micromatch');
// mm.some(list, patterns[, options]);

console.log(mm.some(['foo.js', 'bar.js'], ['*.js', '!foo.js']));
// true
console.log(mm.some(['foo.js'], ['*.js', '!foo.js']));
// false

Returns true if every string in the given list matches any of the given glob patterns.

Params

  • list {String|Array}: The string or array of strings to test.
  • patterns {String|Array}: One or more glob patterns to use for matching.
  • options {Object}: See available options for changing how matches are performed
  • returns {Boolean}: Returns true if all patterns matches all of the strings in list

Example

const mm = require('micromatch');
// mm.every(list, patterns[, options]);

console.log(mm.every('foo.js', ['foo.js']));
// true
console.log(mm.every(['foo.js', 'bar.js'], ['*.js']));
// true
console.log(mm.every(['foo.js', 'bar.js'], ['*.js', '!foo.js']));
// false
console.log(mm.every(['foo.js'], ['*.js', '!foo.js']));
// false

Returns true if all of the given patterns match the specified string.

Params

  • str {String|Array}: The string to test.
  • patterns {String|Array}: One or more glob patterns to use for matching.
  • options {Object}: See available options for changing how matches are performed
  • returns {Boolean}: Returns true if any patterns match str

Example

const mm = require('micromatch');
// mm.all(string, patterns[, options]);

console.log(mm.all('foo.js', ['foo.js']));
// true

console.log(mm.all('foo.js', ['*.js', '!foo.js']));
// false

console.log(mm.all('foo.js', ['*.js', 'foo.js']));
// true

console.log(mm.all('foo.js', ['*.js', 'f*', '*o*', '*o.js']));
// true

Returns an array of matches captured by pattern in string, or null` if the pattern did not match.

Params

  • glob {String}: Glob pattern to use for matching.
  • input {String}: String to match
  • options {Object}: See available options for changing how matches are performed
  • returns {Array|null}: Returns an array of captures if the input matches the glob pattern, otherwise null.

Example

const mm = require('micromatch');
// mm.capture(pattern, string[, options]);

console.log(mm.capture('test/*.js', 'test/foo.js'));
//=> ['foo']
console.log(mm.capture('test/*.js', 'foo/bar.css'));
//=> null

Create a regular expression from the given glob pattern.

Params

  • pattern {String}: A glob pattern to convert to regex.
  • options {Object}
  • returns {RegExp}: Returns a regex created from the given pattern.

Example

const mm = require('micromatch');
// mm.makeRe(pattern[, options]);

console.log(mm.makeRe('*.js'));
//=> /^(?:(\.[\\\/])?(?!\.)(?=.)[^\/]*?\.js)$/

Scan a glob pattern to separate the pattern into segments. Used by the split method.

Params

  • pattern {String}
  • options {Object}
  • returns {Object}: Returns an object with

Example

const mm = require('micromatch');
const state = mm.scan(pattern[, options]);

Parse a glob pattern to create the source string for a regular expression.

Params

  • glob {String}
  • options {Object}
  • returns {Object}: Returns an object with useful properties and output to be used as regex source string.

Example

const mm = require('micromatch');
const state = mm.parse(pattern[, options]);

Process the given brace pattern.

Params

  • pattern {String}: String with brace pattern to process.
  • options {Object}: Any options to change how expansion is performed. See the braces library for all available options.
  • returns {Array}

Example

const { braces } = require('micromatch');
console.log(braces('foo/{a,b,c}/bar'));
//=> [ 'foo/(a|b|c)/bar' ]

console.log(braces('foo/{a,b,c}/bar', { expand: true }));
//=> [ 'foo/a/bar', 'foo/b/bar', 'foo/c/bar' ]

Options

Option Type Default value Description
basename boolean false If set, then patterns without slashes will be matched against the basename of the path if it contains slashes. For example, a?b would match the path /xyz/123/acb, but not /xyz/acb/123.
bash boolean false Follow bash matching rules more strictly - disallows backslashes as escape characters, and treats single stars as globstars (**).
capture boolean undefined Return regex matches in supporting methods.
contains boolean undefined Allows glob to match any part of the given string(s).
cwd string process.cwd() Current working directory. Used by picomatch.split()
debug boolean undefined Debug regular expressions when an error is thrown.
dot boolean false Match dotfiles. Otherwise dotfiles are ignored unless a . is explicitly defined in the pattern.
expandRange function undefined Custom function for expanding ranges in brace patterns, such as {a..z}. The function receives the range values as two arguments, and it must return a string to be used in the generated regex. It's recommended that returned strings be wrapped in parentheses. This option is overridden by the expandBrace option.
failglob boolean false Similar to the failglob behavior in Bash, throws an error when no matches are found. Based on the bash option of the same name.
fastpaths boolean true To speed up processing, full parsing is skipped for a handful common glob patterns. Disable this behavior by setting this option to false.
flags boolean undefined Regex flags to use in the generated regex. If defined, the nocase option will be overridden.
format function undefined Custom function for formatting the returned string. This is useful for removing leading slashes, converting Windows paths to Posix paths, etc.
ignore array|string undefined One or more glob patterns for excluding strings that should not be matched from the result.
keepQuotes boolean false Retain quotes in the generated regex, since quotes may also be used as an alternative to backslashes.
literalBrackets boolean undefined When true, brackets in the glob pattern will be escaped so that only literal brackets will be matched.
lookbehinds boolean true Support regex positive and negative lookbehinds. Note that you must be using Node 8.1.10 or higher to enable regex lookbehinds.
matchBase boolean false Alias for basename
maxLength boolean 65536 Limit the max length of the input string. An error is thrown if the input string is longer than this value.
nobrace boolean false Disable brace matching, so that {a,b} and {1..3} would be treated as literal characters.
nobracket boolean undefined Disable matching with regex brackets.
nocase boolean false Perform case-insensitive matching. Equivalent to the regex i flag. Note that this option is ignored when the flags option is defined.
nodupes boolean true Deprecated, use nounique instead. This option will be removed in a future major release. By default duplicates are removed. Disable uniquification by setting this option to false.
noext boolean false Alias for noextglob
noextglob boolean false Disable support for matching with extglobs (like +(a|b))
noglobstar boolean false Disable support for matching nested directories with globstars (**)
nonegate boolean false Disable support for negating with leading !
noquantifiers boolean false Disable support for regex quantifiers (like a{1,2}) and treat them as brace patterns to be expanded.
onIgnore function undefined Function to be called on ignored items.
onMatch function undefined Function to be called on matched items.
onResult function undefined Function to be called on all items, regardless of whether or not they are matched or ignored.
posix boolean false Support POSIX character classes ("posix brackets").
posixSlashes boolean undefined Convert all slashes in file paths to forward slashes. This does not convert slashes in the glob pattern itself
prepend string undefined String to prepend to the generated regex used for matching.
regex boolean false Use regular expression rules for + (instead of matching literal +), and for stars that follow closing parentheses or brackets (as in )* and ]*).
strictBrackets boolean undefined Throw an error if brackets, braces, or parens are imbalanced.
strictSlashes boolean undefined When true, picomatch won't match trailing slashes with single stars.
unescape boolean undefined Remove preceding backslashes from escaped glob characters before creating the regular expression to perform matches.
unixify boolean undefined Alias for posixSlashes, for backwards compatitibility.

Options Examples

options.basename

Allow glob patterns without slashes to match a file path based on its basename. Same behavior as minimatch option matchBase.

Type: Boolean

Default: false

Example

micromatch(['a/b.js', 'a/c.md'], '*.js');
//=> []

micromatch(['a/b.js', 'a/c.md'], '*.js', { basename: true });
//=> ['a/b.js']

options.bash

Enabled by default, this option enforces bash-like behavior with stars immediately following a bracket expression. Bash bracket expressions are similar to regex character classes, but unlike regex, a star following a bracket expression does not repeat the bracketed characters. Instead, the star is treated the same as any other star.

Type: Boolean

Default: true

Example

const files = ['abc', 'ajz'];
console.log(micromatch(files, '[a-c]*'));
//=> ['abc', 'ajz']

console.log(micromatch(files, '[a-c]*', { bash: false }));

options.expandRange

Type: function

Default: undefined

Custom function for expanding ranges in brace patterns. The fill-range library is ideal for this purpose, or you can use custom code to do whatever you need.

Example

The following example shows how to create a glob that matches a numeric folder name between 01 and 25, with leading zeros.

const fill = require('fill-range');
const regex = micromatch.makeRe('foo/{01..25}/bar', {
  expandRange(a, b) {
    return `(${fill(a, b, { toRegex: true })})`;
  }
});

console.log(regex)
//=> /^(?:foo\/((?:0[1-9]|1[0-9]|2[0-5]))\/bar)$/

console.log(regex.test('foo/00/bar')) // false
console.log(regex.test('foo/01/bar')) // true
console.log(regex.test('foo/10/bar')) // true
console.log(regex.test('foo/22/bar')) // true
console.log(regex.test('foo/25/bar')) // true
console.log(regex.test('foo/26/bar')) // false

options.format

Type: function

Default: undefined

Custom function for formatting strings before they're matched.

Example

// strip leading './' from strings
const format = str => str.replace(/^\.\//, '');
const isMatch = picomatch('foo/*.js', { format });
console.log(isMatch('./foo/bar.js')) //=> true

options.ignore

String or array of glob patterns to match files to ignore.

Type: String|Array

Default: undefined

const isMatch = micromatch.matcher('*', { ignore: 'f*' });
console.log(isMatch('foo')) //=> false
console.log(isMatch('bar')) //=> true
console.log(isMatch('baz')) //=> true

options.matchBase

Alias for options.basename.

options.noextglob

Disable extglob support, so that extglobs are regarded as literal characters.

Type: Boolean

Default: undefined

Examples

console.log(micromatch(['a/z', 'a/b', 'a/!(z)'], 'a/!(z)'));
//=> ['a/b', 'a/!(z)']

console.log(micromatch(['a/z', 'a/b', 'a/!(z)'], 'a/!(z)', { noextglob: true }));
//=> ['a/!(z)'] (matches only as literal characters)

options.nonegate

Disallow negation (!) patterns, and treat leading ! as a literal character to match.

Type: Boolean

Default: undefined

options.noglobstar

Disable matching with globstars (**).

Type: Boolean

Default: undefined

micromatch(['a/b', 'a/b/c', 'a/b/c/d'], 'a/**');
//=> ['a/b', 'a/b/c', 'a/b/c/d']

micromatch(['a/b', 'a/b/c', 'a/b/c/d'], 'a/**', {noglobstar: true});
//=> ['a/b']

options.nonull

Alias for options.nullglob.

options.nullglob

If true, when no matches are found the actual (arrayified) glob pattern is returned instead of an empty array. Same behavior as minimatch option nonull.

Type: Boolean

Default: undefined

options.onIgnore

const onIgnore = ({ glob, regex, input, output }) => {
  console.log({ glob, regex, input, output });
  // { glob: '*', regex: /^(?:(?!\.)(?=.)[^\/]*?\/?)$/, input: 'foo', output: 'foo' }
};

const isMatch = micromatch.matcher('*', { onIgnore, ignore: 'f*' });
isMatch('foo');
isMatch('bar');
isMatch('baz');

options.onMatch

const onMatch = ({ glob, regex, input, output }) => {
  console.log({ input, output });
  // { input: 'some\\path', output: 'some/path' }
  // { input: 'some\\path', output: 'some/path' }
  // { input: 'some\\path', output: 'some/path' }
};

const isMatch = micromatch.matcher('**', { onMatch, posixSlashes: true });
isMatch('some\\path');
isMatch('some\\path');
isMatch('some\\path');

options.onResult

const onResult = ({ glob, regex, input, output }) => {
  console.log({ glob, regex, input, output });
};

const isMatch = micromatch('*', { onResult, ignore: 'f*' });
isMatch('foo');
isMatch('bar');
isMatch('baz');

options.posixSlashes

Convert path separators on returned files to posix/unix-style forward slashes. Aliased as unixify for backwards compatibility.

Type: Boolean

Default: true on windows, false everywhere else.

Example

console.log(micromatch.match(['a\\b\\c'], 'a/**'));
//=> ['a/b/c']

console.log(micromatch.match(['a\\b\\c'], { posixSlashes: false }));
//=> ['a\\b\\c']

options.unescape

Remove backslashes from escaped glob characters before creating the regular expression to perform matches.

Type: Boolean

Default: undefined

Example

In this example we want to match a literal *:

console.log(micromatch.match(['abc', 'a\\*c'], 'a\\*c'));
//=> ['a\\*c']

console.log(micromatch.match(['abc', 'a\\*c'], 'a\\*c', { unescape: true }));
//=> ['a*c']


Extended globbing

Micromatch supports the following extended globbing features.

Extglobs

Extended globbing, as described by the bash man page:

pattern regex equivalent description
?(pattern) (pattern)? Matches zero or one occurrence of the given patterns
*(pattern) (pattern)* Matches zero or more occurrences of the given patterns
+(pattern) (pattern)+ Matches one or more occurrences of the given patterns
@(pattern) (pattern) * Matches one of the given patterns
!(pattern) N/A (equivalent regex is much more complicated) Matches anything except one of the given patterns

* Note that @ isn't a regex character.

Braces

Brace patterns can be used to match specific ranges or sets of characters.

Example

The pattern {f,b}*/{1..3}/{b,q}* would match any of following strings:

foo/1/bar
foo/2/bar
foo/3/bar
baz/1/qux
baz/2/qux
baz/3/qux

Visit braces to see the full range of features and options related to brace expansion, or to create brace matching or expansion related issues.

Regex character classes

Given the list: ['a.js', 'b.js', 'c.js', 'd.js', 'E.js']:

  • [ac].js: matches both a and c, returning ['a.js', 'c.js']
  • [b-d].js: matches from b to d, returning ['b.js', 'c.js', 'd.js']
  • a/[A-Z].js: matches and uppercase letter, returning ['a/E.md']

Learn about regex character classes.

Regex groups

Given ['a.js', 'b.js', 'c.js', 'd.js', 'E.js']:

  • (a|c).js: would match either a or c, returning ['a.js', 'c.js']
  • (b|d).js: would match either b or d, returning ['b.js', 'd.js']
  • (b|[A-Z]).js: would match either b or an uppercase letter, returning ['b.js', 'E.js']

As with regex, parens can be nested, so patterns like ((a|b)|c)/b will work. Although brace expansion might be friendlier to use, depending on preference.

POSIX bracket expressions

POSIX brackets are intended to be more user-friendly than regex character classes. This of course is in the eye of the beholder.

Example

console.log(micromatch.isMatch('a1', '[[:alpha:][:digit:]]')) //=> true
console.log(micromatch.isMatch('a1', '[[:alpha:][:alpha:]]')) //=> false

Notes

Bash 4.3 parity

Whenever possible matching behavior is based on behavior Bash 4.3, which is mostly consistent with minimatch.

However, it's suprising how many edge cases and rabbit holes there are with glob matching, and since there is no real glob specification, and micromatch is more accurate than both Bash and minimatch, there are cases where best-guesses were made for behavior. In a few cases where Bash had no answers, we used wildmatch (used by git) as a fallback.

Backslashes

There is an important, notable difference between minimatch and micromatch in regards to how backslashes are handled in glob patterns.

  • Micromatch exclusively and explicitly reserves backslashes for escaping characters in a glob pattern, even on windows, which is consistent with bash behavior. More importantly, unescaping globs can result in unsafe regular expressions.
  • Minimatch converts all backslashes to forward slashes, which means you can't use backslashes to escape any characters in your glob patterns.

We made this decision for micromatch for a couple of reasons:

  • Consistency with bash conventions.
  • Glob patterns are not filepaths. They are a type of regular language that is converted to a JavaScript regular expression. Thus, when forward slashes are defined in a glob pattern, the resulting regular expression will match windows or POSIX path separators just fine.

A note about joining paths to globs

Note that when you pass something like path.join('foo', '*') to micromatch, you are creating a filepath and expecting it to still work as a glob pattern. This causes problems on windows, since the path.sep is \\.

In other words, since \\ is reserved as an escape character in globs, on windows path.join('foo', '*') would result in foo\\*, which tells micromatch to match * as a literal character. This is the same behavior as bash.

To solve this, you might be inspired to do something like 'foo\\*'.replace(/\\/g, '/'), but this causes another, potentially much more serious, problem.

Benchmarks

Running benchmarks

Install dependencies for running benchmarks:

$ cd bench && npm install

Run the benchmarks:

$ npm run bench

Latest results

As of July 12, 2023 (longer bars are better):

# .makeRe star
  micromatch x 2,232,802 ops/sec ±2.34% (89 runs sampled))
  minimatch x 781,018 ops/sec ±6.74% (92 runs sampled))

# .makeRe star; dot=true
  micromatch x 1,863,453 ops/sec ±0.74% (93 runs sampled)
  minimatch x 723,105 ops/sec ±0.75% (93 runs sampled)

# .makeRe globstar
  micromatch x 1,624,179 ops/sec ±2.22% (91 runs sampled)
  minimatch x 1,117,230 ops/sec ±2.78% (86 runs sampled))

# .makeRe globstars
  micromatch x 1,658,642 ops/sec ±0.86% (92 runs sampled)
  minimatch x 741,224 ops/sec ±1.24% (89 runs sampled))

# .makeRe with leading star
  micromatch x 1,525,014 ops/sec ±1.63% (90 runs sampled)
  minimatch x 561,074 ops/sec ±3.07% (89 runs sampled)

# .makeRe - braces
  micromatch x 172,478 ops/sec ±2.37% (78 runs sampled)
  minimatch x 96,087 ops/sec ±2.34% (88 runs sampled)))

# .makeRe braces - range (expanded)
  micromatch x 26,973 ops/sec ±0.84% (89 runs sampled)
  minimatch x 3,023 ops/sec ±0.99% (90 runs sampled))

# .makeRe braces - range (compiled)
  micromatch x 152,892 ops/sec ±1.67% (83 runs sampled)
  minimatch x 992 ops/sec ±3.50% (89 runs sampled)d))

# .makeRe braces - nested ranges (expanded)
  micromatch x 15,816 ops/sec ±13.05% (80 runs sampled)
  minimatch x 2,953 ops/sec ±1.64% (91 runs sampled)

# .makeRe braces - nested ranges (compiled)
  micromatch x 110,881 ops/sec ±1.85% (82 runs sampled)
  minimatch x 1,008 ops/sec ±1.51% (91 runs sampled)

# .makeRe braces - set (compiled)
  micromatch x 134,930 ops/sec ±3.54% (63 runs sampled))
  minimatch x 43,242 ops/sec ±0.60% (93 runs sampled)

# .makeRe braces - nested sets (compiled)
  micromatch x 94,455 ops/sec ±1.74% (69 runs sampled))
  minimatch x 27,720 ops/sec ±1.84% (93 runs sampled))

Contributing

All contributions are welcome! Please read the contributing guide to get started.

Bug reports

Please create an issue if you encounter a bug or matching behavior that doesn't seem correct. If you find a matching-related issue, please:

  • research existing issues first (open and closed)
  • visit the GNU Bash documentation to see how Bash deals with the pattern
  • visit the minimatch documentation to cross-check expected behavior in node.js
  • if all else fails, since there is no real specification for globs we will probably need to discuss expected behavior and decide how to resolve it. which means any detail you can provide to help with this discussion would be greatly appreciated.

Platform issues

It's important to us that micromatch work consistently on all platforms. If you encounter any platform-specific matching or path related issues, please let us know (pull requests are also greatly appreciated).

About

Contributing

Pull requests and stars are always welcome. For bugs and feature requests, please create an issue.

Please read the contributing guide for advice on opening issues, pull requests, and coding standards.

Running Tests

Running and reviewing unit tests is a great way to get familiarized with a library and its API. You can install dependencies and run tests with the following command:

$ npm install && npm test
Building docs

(This project's readme.md is generated by verb, please don't edit the readme directly. Any changes to the readme must be made in the .verb.md readme template.)

To generate the readme, run the following command:

$ npm install -g verbose/verb#dev verb-generate-readme && verb

Related projects

You might also be interested in these projects:

  • braces: Bash-like brace expansion, implemented in JavaScript. Safer than other brace expansion libs, with complete support… more | homepage
  • expand-brackets: Expand POSIX bracket expressions (character classes) in glob patterns. | homepage
  • extglob: Extended glob support for JavaScript. Adds (almost) the expressive power of regular expressions to glob… more | homepage
  • fill-range: Fill in a range of numbers or letters, optionally passing an increment or step to… more | homepage
  • nanomatch: Fast, minimal glob matcher for node.js. Similar to micromatch, minimatch and multimatch, but complete Bash… more | homepage

Contributors

Commits Contributor
515 jonschlinkert
12 es128
9 danez
8 doowb
6 paulmillr
5 mrmlnc
3 DrPizza
2 TrySound
2 mceIdo
2 Glazy
2 MartinKolarik
2 antonyk
2 Tvrqvoise
1 amilajack
1 Cslove
1 devongovett
1 DianeLooney
1 UltCombo
1 frangio
1 joyceerhl
1 juszczykjakub
1 muescha
1 sebdeckers
1 tomByrer
1 fidian
1 curbengh
1 simlu
1 wtgtybhertgeghgtwtg
1 yvele

Author

Jon Schlinkert

License

Copyright © 2023, Jon Schlinkert. Released under the MIT License.


This file was generated by verb-generate-readme, v0.8.0, on July 12, 2023.

micromatch's People

Contributors

antonyk avatar curbengh avatar danez avatar devongovett avatar dianelooney avatar donatj avatar doowb avatar drpizza avatar es128 avatar fidian avatar frangio avatar glazy avatar jonschlinkert avatar joyceerhl avatar juszczykjakub avatar martinkolarik avatar mceido avatar mrmlnc avatar muescha avatar paulmillr avatar sebdeckers avatar simlu avatar styfle avatar tombyrer avatar trysound avatar tvrqvoise avatar ultcombo avatar wtgtybhertgeghgtwtg avatar yvele avatar zoomertedjackson avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

micromatch's Issues

Directory begin with dot

Hi !

Strange behavior since 2.2.0 :

> mm.isMatch('.tmp/scripts/app.js', '.tmp/scripts/**/*.js');
false

in 2.1.6 :

> mm.isMatch('.tmp/scripts/app.js', '.tmp/scripts/**/*.js');
true

Is that normal ?

Thx

problem with "logical OR" or problem in my mind, lol?

I use makeRe to generate regex based on glob pattern to test against some filepath.

examples

var expected = false;
var options = {};
var pattern = 'maiden/{**/*.,*.}';
var re = mm.makeRe(pattern, options);
console.log(re.test('maiden/code'));
//=> true

isMatch()

var expected = false;
var options = {};
var pattern = 'maiden/{**/*.,*.}';
var match = mm.isMatch('maiden/code', pattern, options);
console.log(match);
//=> true

micromatch()

var expected = [];
var options = {};
var pattern = 'maiden/{**/*.,*.}';
var match = mm('maiden/code', pattern, options);
console.log(match);
//=> ['maiden/code']

I think its logical to return true only if there no dots in the pattern, ie 'maiden/{**/*,*}'

Release 2.2.0

Just trying to gather all the outstanding points discussed recently to be resolved prior to release. Anything is still open to discussion if there remains any disagreement about any of these points.

@jonschlinkert In the future if you want to do your changes in branches/PRs I'd be happy to review and I think it would make it easier to keep all feedback and resolution organized.

  • Ensure extglob, braces, and brackets parsing are enabled by default
  • Drop the options as above in favor of the no* alternatives
  • Support nobrace option as alias for nobraces for minimatch parity
  • Tests to ensure both nobrace and nobraces remain supported at least until a major version bump
  • Ensure readme documentation accurately reflects all of the above
  • Fix readme anchor links
  • Update benchmarks & browser build

The glob string */*/** fails to match a lot of things

const micromatch = require('micromatch');

// create a matcher that should return true for any
// file that's inside at least two nested directories...
const match = micromatch.matcher('*/*/**');

// it's correct for these paths:
match('a/b.txt'); // false
match('a/b/c.txt'); // true

// but it stops matching if you add more levels, despite double-star:
match('a/b/c/d.txt'); // false (expected true)
match('a/b/c/d/e.txt'); // false (expected true)

Live demo of this bug on Tonic

Update is-glob

I just updated my glob-parent dependency in glob-stream and was warned about micromatch requiring a different version. Thought I'd give the heads up.

[:punct:] expanded incorrectly

[:punct:] is changed to [!"#$%&\'()\\*+,-./:;<=>?@[\\]^_{|}~][here](https://github.com/jonschlinkert/micromatch/blob/17f06276a9a1fc8858582612d73aec5abf8744c6/lib/expand.js#L117) and because it starts with[!` it's changed to the negated version right after. I suppose the most simple fix would be changing order of the characters in the regex class.

dot not properly escaped in expandFilename

These should return false

> mm.isMatch('zzjs', 'z*.js')
true
> mm.isMatch('zzjs', '*z.js')
true

With a directory in the pattern, it behaves correctly because the dot gets escaped

> mm.isMatch('a/zzjs', 'a/*z.js')
false
> mm.isMatch('a/zzjs', 'a/z*.js')
false

problem with re-include, excluded path

Because I still working on glob-fs idea :D lol
Actually it works on 80% of the common usage of gulp/glob-stream, fails only on complex fixtures, or no logical tests (look at you glob-stream, nah.. it have very very weird tests).
Btw, talking about that, can you answer me why is needed to ignore negate glob if it is first in given patterns?!
No logic for me... nor of matching libs (micromatch/minimatch/node-glob) have this behaving.. lol.

On topic

var micromatch = require('micromatch')
var multimatch = require('multimatch')

var paths = [
  'foo/',
  'foo/bar.js',
  'foo/bar.md',
  'foo/bar.txt',
  'foo/bar.hbs',
  'foo/bar.json',
  'foo/bar.coffee',
  'foo/bar/',
  'foo/bar/bar.js',
  'foo/bar/bar.md',
  'foo/bar/bar.txt',
  'foo/bar/bar.hbs',
  'foo/bar/bar.json',
  'foo/bar/bar.coffee',
];

var patterns = [
  'foo/**',
  '!foo/',
  '!foo/bar/',
  '!foo/bar/*.{j*,txt,hbs}',
  'foo/bar/*.json',
];

var res = micromatch(paths, patterns);

console.log(res, res.length);

micromatch, note there foo/bar/bar.json missing

[ 'foo/bar.js',
  'foo/bar.md',
  'foo/bar.txt',
  'foo/bar.hbs',
  'foo/bar.json',
  'foo/bar.coffee',
  'foo/bar/bar.md',
  'foo/bar/bar.coffee' ] 8

multimatch, all is okey

[ 'foo/bar.js',
  'foo/bar.md',
  'foo/bar.txt',
  'foo/bar.hbs',
  'foo/bar.json',
  'foo/bar.coffee',
  'foo/bar/bar.md',
  'foo/bar/bar.coffee',
  'foo/bar/bar.json' ] 9

make patterns the first arg?

This is a major breaking change, and it's probably a bad idea given that minimatch has gotten everyone used to passing patterns as the second arg, but I've always strongly disliked it and found it confusing.

I'm curious if anyone else agrees with this.

This is the current signature, with pattern(s) usually the second arg:

mm(['a/b/a.md', 'a/b/b.md', 'a/b/c.md', 'a/b/d.md', ], '**/*.md');

I think it makes more sense like this:

mm('**/*.md', ['a/b/a.md', 'a/b/b.md', 'a/b/c.md', 'a/b/d.md']);

This signature makes using the lib more consistent when arguments are partially applied to create matching functions, like var isMatch = matcher('foo/*.md'); which returns a function that could be passed to Array#filter for example.

Also, passing the pattern first feels more natural when regex is used instead of a glob pattern.

mm(/\.md$/, ['a/b/a.md', 'a/b/b.md', 'a/b/c.md', 'a/b/d.md']);

What's the purpose, idea behind?

Is the purpose is to be completely compatible with minimatch and pass it's tests?

Because I think minimatch support too much cases for one simple usage like glob filepaths. I fork the repo and made some basic implementation and tests.

It would be great if you come with more test cases. :)

Partial wildcard bug (without globstar)

Uncovered by @tunnckoCore in #15 (thank you). Opening a new issue to track resolution.

console.log(micromatch.isMatch('a/z.js', 'a/z*.js'));
//=> should be true
console.log(micromatch(paths, '*/z*.js'));
//=> should be [ 'a/z.js' ]
// multimatch

console.log(multimatch(paths, '*/z*.js'));
//=> [ 'a/z.js' ]

Problems with $

> mm.isMatch('$', '$')
true
> mm.isMatch('$/foo', '$/*')
false
> mm.isMatch('a/foo', 'a/*')
true
> mm.isMatch('$/foo', '$/*')
false
> mm.isMatch('$foo/foo', '$foo/*')
false
> mm.isMatch('foo$/foo', 'foo$/*')
false
> mm.isMatch('foo/foo', 'foo/*')
true

paulmillr/chokidar#357

path variables

Consider supporting bash-like path variables, ex. ${foo}. Should be easy to do since the syntax is exactly the same as es6 variables.

Dot directory and {* /} combination is not working

Dot directory and {* /} combination is not working

Start dot directory, failed.

> mm.isMatch('.a/xyz.md', '.a/{,*/}xyz.md')
false
> mm.isMatch('.a/xyz.md', '.a/**/xyz.md')
false

Start not dot directory, success.

> mm.isMatch('a/xyz.md', 'a/{,*/}xyz.md')
true
> mm.isMatch('a/xyz.md', 'a/**/xyz.md')
true

regression v2.2.0

Possible regression with default micromatch options. #27 (comment)

The first two examples don't match anymore after upgrading to v2.2.0.
Looks like it doesn't match when pattern starts with globstar (**) and no slashes (/) are present in the pattern.

v2.2.0

micromatch(['/api/foo/bar.html'], '**.*')          //  regression?
//=> []

micromatch(['/api/foo/bar.html'], '**.html')       //  regression?
//=> []

micromatch(['/api/foo/bar.html'], '/**.*')
//=> ['/api/foo/bar.html']

micromatch(['/api/foo/bar.html'], '/**.html')
//=> ['/api/foo/bar.html']

micromatch(['/api/foo/bar.html'], '/**/*.*')
//=> ['/api/foo/bar.html']

v2.1.6

micromatch(['/api/foo/bar.html'], '**.*')
//=> ['/api/foo/bar.html']

micromatch(['/api/foo/bar.html'], '**.html')
//=> ['/api/foo/bar.html']

micromatch(['/api/foo/bar.html'], '/**.*')
//=> ['/api/foo/bar.html']

micromatch(['/api/foo/bar.html'], '/**.html')
//=> ['/api/foo/bar.html']

micromatch(['/api/foo/bar.html'], '/**/*.*')
//=> ['/api/foo/bar.html']

re-organize tests

unit tests and file names need to be organized differently to make it easier to test for regressions and new features.

globstar and trailing slash

From #62

var micromatch = require('micromatch')
var isMatch = micromatch.matcher('foo/bar/**')
console.log(isMatch('foo/bar')) // => false, i think it make sense to pass?
console.log(isMatch('foo/bar/')) // => true
console.log(isMatch('foo/bar/baz')) // => true
console.log(isMatch('foo/bar/baz/fez')) // => true
console.log(isMatch('foo/bar/baz/qux.js')) // => true

If that's correct behaving, okey, but you are forced to do some hacks like #62 (comment) and it not make sense for me.

edit: and ** means anything or empty - same as single *. so basically if it make sense to match with trailing slash it make sense to match without it, because it is absolutely the same - in anyway it is the dir.

nodupes option not work as expected?

Heya, not sure enough be I have one snippet here...

var files = [
  '.editorconfig',
  '.git',
  '.gitignore',
  '.nyc_output',
  '.travis.yml',
  '.verb.md',
  'CHANGELOG.md',
  'CONTRIBUTING.md',
  'LICENSE',
  'coverage',
  'example.js',
  'example.md',
  'example.css',
  'index.js',
  'node_modules',
  'package.json',
  'test.js',
  'utils.js'
]

console.log(micromatch(files, ['example.*', '*.js'], {
  nodupes: true
}))

result (outputs example.js twice?)

[ 'example.js',
  'example.md',
  'example.css',
  'example.js',
  'index.js',
  'test.js',
  'utils.js' ]

Issue with wildcard + negated extglob

Using v2.1.6

> mm.isMatch('src/a/b/c.js', 'src/**/*!(_test).js')
false
> mm.isMatch('src/a/b/c_test.js', 'src/**/*!(_test).js')
false

Using master branch

> mm.isMatch('src/a/b/c.js', 'src/**/*!(_test).js')
true
> mm.isMatch('src/a/b/c_test.js', 'src/**/*!(_test).js')
true

Specifying extglob: true or extglob: false does not appear to have any impact. When the * is removed before the ! it behaves as I'd expect.

paulmillr/chokidar#58

Double globstar bug

From paulmillr/chokidar#283

> mm.isMatch('markup/modules/exampleModule/assets/image.png', 'markup/modules/**/assets/**/*.*')
false
// should be true

// these are ok:
> mm.isMatch('markup/modules/exampleModule/assets/subDir/image.png', 'markup/modules/**/assets/**/*.*')
true
> mm.isMatch('markup/modules/exampleModule/assets/subDir/subDir/image.png', 'markup/modules/**/assets/**/*.*')
true

possibility `.filter` to accept array glob pattern

Like...

[
  'fs-readdir-callback-api.js',
  'fs-readdir-stream-api.js',
  'glob-stream.js',
  'readdirp-callback-api.js',
  'readdirp-stream-api.js',
  'recursive-readdir.js'
].filter(micromatch.filter(['*', '!*api*']))
//=> ['glob-stream.js', 'recursive-readdir.js']

Use case if .filter accepts array
this part of recursive-readdir package would become something like this

var ignoreOpts = {dot: true, matchBase: true};
var nonIgnores = ignores.filter(function(ignore) {
  return ignore.chatAt(0) !== '!';
})
var ignored = map(nonIgnores, function(ignore) {
  return '!' + ignore;
});
ignores = [].concat([ignores, ignored])
var ignoreFilter = micromatch.filter(ignores, ignoreOpts)

files.filter(ignoreFilter).forEach(function (file) {
  // ... another code below

Partial matching

When implementing a glob-walker, it'd be useful if we were able to tell that files in a specific directory will never match the pattern, without trying to match all of them.

E.g., with a pattern aaa/{bbb,ccc}/**/*.js, we could immediately discard folder aaa/ddd, without listing and matching everything inside, which would greatly reduce the number of fs operations.

I tried to implement a flag mightMatch, which would change the behavior to returning true if filepath matches the beginning of the pattern and false if it doesn't (for aaa/bbb the generated RegExp would be something like /^(?:\/$|(?:aaa(\/bbb)?)?)$/), but I couldn't get it working in all edge cases.

Is there any chance you could add such function, or at least suggest where would be the right place to implement this?

Double globstar does not play well with backslashes

This seems to be a bug.

mm('/user.js', '**.js')
// expected => true
// got      => false

 

Everything works great if a / is nowhere in the string; as seen below.

mm('user.js', '**.js')
// expected => true
// got      => true

 

Using **/*.js instead is a workaround.

mm('/user.js', '**/*.js')
// expected => true
// got      => true

mm('user.js', '**/*.js')
// expected => true
// got      => true

 

NodeJS v0.12.4
micromatch v2.2.0

false on regex group matching

with is-match

var matcher = require('is-match')
var isMatch = matcher(['123.[71-79].34.*'])

console.log(isMatch('123.77.34.89'))
//=> false

globstar

AFAIK, the double star should only match multiple directories if it' the only thing in a path part, e.g., a/**/b, but not a/b**.

In micromatch, it seems it can be followed by other characters:

mm.isMatch('a/b/c', 'a/b**'); // => returns false
mm.isMatch('a/c/b', 'a/**b'); // => returns true (maybe a bug?)

Is this intentional?

Array with negation pattern

As you noted in level-glob#1 (thanks!), there's a possible bug (I'm not sure either) when using multiple patterns and negation. I did some tests with both 1.0.1 and 1.4.2, and it comes down to the following. These two lines produce different results:

var mm = require('micromatch');
console.log(mm.match(['a.md', 'b.js'], ['!*.md']));
console.log(mm.match(['a.md', 'b.js'], '!*.md'));

The first matches nothing, the second matches b.js. Is this expected behavior?

how to get the contains matched string

The current contains method just returns true or false, is there anyway to get the contains string.

For example:

// Old style
mm.contains('a/b/c', 'a/*');
//=> true

// New Style
mm.contains('a/b/c', 'a/*');
//=> a/b

In my case, I just want to replace the matched string with empty

problem (not so) matching urls

I realize that it is because of filepaths globbing idea, but it's uncomfortable when trying to match urls.

var matcher = require('is-match')

matcher('https://github.com/*')('https://github.com/tunnckoCore')
//=> false

matcher('https://github.com**/**')('https://github.com/tunnckoCore')
//=> false

matcher('https://github.co**/**')('https://github.com/tunnckoCore')
//=> false

matcher('https://github.com/**/**')('https://github.com/tunnckoCore')
//=> false

matcher('https://github.com/**/*')('https://github.com/tunnckoCore')
//=> false

matcher('http*')('https://foo.com')
//=> false

matcher('http**/*')('https://foo.com')
//=> false

matcher('http*/**')('https://foo.com')
//=> true

matcher('http**/**')('https://foo.com')
//=> true

using chorks/is-match#master (waiting merge PR) which uses micromatch v2.1.6

Maybe Im missing some option? Or we should add some option? :D

Bug with partial wildcards

> mm.isMatch('../test-fixtures/add.txt', '../test-fixtures/**/a*.txt')
true
> mm.isMatch('../test-fixtures/add.txt', '../test-*/**/a*.txt')
false
> mm.isMatch('../test-fixtures/subdir/subsub/a.txt', '../test-*/**/a*.txt')
false
> mm.isMatch('../test-fixtures/subdir/subsub/ab.txt', '../test-*/**/a*.txt')
true

Realized this is the cause of a few newly failing tests in chokidar

seeing utils.isGlob error with versions of micromatch > 2.3.1

Note, this error does not occur with 2.1.6, but has occurred since 2.3.1:

TypeError: lazy-cache utils.isGlob is not a function /Users/benjamincoe/bcoe/nyc/node_modules/micromatch/node_modules/lazy-cache/index.js
    at matcher (/Users/benjamincoe/bcoe/nyc/node_modules/micromatch/index.js:301:14)
    at Function.any (/Users/benjamincoe/bcoe/nyc/node_modules/micromatch/index.js:239:19)
    at NYC.shouldInstrumentFile (/Users/benjamincoe/bcoe/nyc/index.js:136:25)
    at NYC.addFile (/Users/benjamincoe/bcoe/nyc/index.js:98:25)
    at Object.defaultHook (/Users/benjamincoe/bcoe/nyc/index.js:163:21)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Function.getter (/Users/benjamincoe/bcoe/nyc/node_modules/micromatch/node_modules/lazy-cache/index.js:32:31)

Whitespace in path

Hi, I'm trying to match files using the following pattern:

require('micromatch')('/Users/tobiasreich/Sites/aaa/bbb/ccc 2016/src/de.ejs', [
    '/Users/tobiasreich/Sites/aaa/bbb/ccc 2016/src/**/[^_]*.{html,ejs}'
]) // => []

micromatch sadly returns an empty array, which is not what I expected. After several experiments I figured out that the whitespace between "ccc" and "2016" might be the reason for it.

require('micromatch')('/Users/tobiasreich/Sites/aaa/bbb/ccc2016/src/de.ejs', [
    '/Users/tobiasreich/Sites/aaa/bbb/ccc2016/src/**/[^_]*.{html,ejs}'
]) // => ['/Users/tobiasreich/Sites/aaa/bbb/ccc2016/src/de.ejs']

Is this a problem of the pattern I'm using or an issue of micromatch? How should I deal with spaces in paths?

Node.js Version: 6.2
micromatch Version: 2.3.8

bug when absolute path and dot option true/false

var path = require('path')
var absolute = true

var filepath = absolute ? path.resolve('.git') : '.git'
var pattern = absolute ? path.resolve('**') : '**'

console.log(filepath)
console.log(pattern)

var matches = mm(filepath, pattern, {dot: false})
var ismatch = mm.isMatch(filepath, pattern, {dot: false})
var reEnabled = mm.makeRe(filepath, {dot: true})
var reDisabled = mm.makeRe(filepath, {dot: false})

console.log(matches) // => [ '/home/charlike/dev/final/glob-fs/.git' ]
console.log(ismatch) // => true
console.log(reEnabled.test(filepath)) // => true
console.log(reDisabled.test(filepath)) // => true
console.log(reEnabled)  // => /^(?:\/home\/charlike\/dev\/final\/glob-fs\/\.git)$/
console.log(reDisabled) // => /^(?:\/home\/charlike\/dev\/final\/glob-fs\/\.git)$/

Try out to change absolute to false and you get empty array. Which is the correct behaving when dot: false. But when absolute path and absolute pattern is passed it find match when dot: false.

Travis Error: Failed resolving git HEAD (https://github.com/jonschlinkert/micromatch

Just got this error in our Travis build, it's a subdependency (karma - anymatch - micromatch )

npm ERR! Failed resolving git HEAD (https://github.com/jonschlinkert/micromatch) fatal: ambiguous argument '2.3.0': unknown revision or path not in the working tree.

npm ERR! Failed resolving git HEAD (https://github.com/jonschlinkert/micromatch) Use '--' to separate paths from revisions, like this:

npm ERR! Failed resolving git HEAD (https://github.com/jonschlinkert/micromatch) 'git <command> [<revision>...] -- [<file>...]'

npm ERR! Failed resolving git HEAD (https://github.com/jonschlinkert/micromatch) 

This issue probably do not belong here, but I put it here for others to be aware of the issue

Could this be a version mismatch at your end, or is this a result of bad dep version range in a dependency?

Issue when using negations against /'s

This might just be me being stupid, but I want to check :)

Can someone please clarify the state of these two globs? Afaik they should both match?

# matches
mm.any('/target/build', ['/target/!(dist)'])

# doesn't match
mm.any('/target/build/classes', ['/target/!(dist)'])

I'm not too familiar with globs so maybe I'm missing something. I guess the potential to have a /... after is throwing it off?

mm.any('/target/build/classes', ['!/target/dist']) matches too, but in my use case the /target/ prefix might be changing, so I can't just hardcode that section of the pattern.

Thanks in advance! Great library, very nice to use.

cwd option

Do you have plans to support a cwd option?

Otherwise it is a bit unclear where the fs lookup is performed.

2.3.6 housekeeping

for starters...

  • replace gulp-jshint with gulp-eslint
  • lint (I expect this to result in a bunch of small changes since we'll be using a much more stringent linting config)

I'm planning on doing this in the next patch. anything to add @es128?

** sometimes matches dotfiles

From #62:

mm.isMatch('/aaa/bbb/.git', '/aaa/bbb/**'); // => true; should be false
mm.isMatch('aaa/bbb/.git', 'aaa/bbb/**'); // => true; should be false
mm.isMatch('/aaa/bbb/ccc/.git', '/aaa/bbb/**'); // => false; correct

array of globs for matcher

Public api should also accept precompiled array of globs for matcher like filter. API parts should be similar, I think.

What is the difference between matcher and filter?

This might be a documentation issue, or maybe I'm being stupid.

The readme says that .matcher(pattern) gets you a function that you can use to match paths. I'm assuming this means it returns true/false, in which case it sounds like it could be used as an array filter function.

But then there seems to be another method for this exact purpose, .filter(): "Returns a function that can be passed to Array#filter()." I don't get it. Can't the returned function from .matcher be used in this way?

What's the difference?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.