Learn about our RFC process, Open RFC meetings & more.Join in the discussion! »


2.0.0 • Public • Published

micromatch NPM version Build Status

Glob matching for javascript/node.js. A faster alternative to minimatch (10-45x faster on avg), with all the features you're used to using in your Grunt and gulp tasks.


Micromatch is 10-55x faster than minimatch, resulting from a combination of caching, tokenization, parsing, runtime compilation and regex optimization strategies.

  • Drop-in replacement for minimatch and multimatch
  • Built-in support for multiple glob patterns, like ['foo/*.js', '!bar.js']
  • Better support for the Bash 4.3 specification, and less buggy
  • Extensive unit tests (approx. 1,300 tests). Minimatch fails many of the tests.


Mainstream glob features:

  • Brace Expansion (foo/bar-{1..5}.md, one/{two,three}/four.md)
  • Typical glob patterns, like **/*, a/b/*.js, or ['foo/*.js', '!bar.js']

Extended globbing features:

  • Logical OR (foo/bar/(abc|xyz).js)
  • Regex character classes (foo/bar/baz-[1-5].js)
  • POSIX bracket expressions (**/[[:alpha:][:digit:]]/)
  • extglobs (**/+(x|y), !(a|b), etc)

You can combine these to create whatever matching patterns you need.

Install with npm

npm i micromatch --save


var mm = require('micromatch');
mm(array, patterns);


mm(['a.js', 'b.md', 'c.txt'], '*.{js,txt}');
//=> ['a.js', 'c.txt']

Multiple patterns

Multiple patterns can also be passed:

mm(['a.md', 'b.js', 'c.txt', 'd.json'], ['*.md', '*.txt']);
//=> ['a.md', 'c.txt']

Negation patterns:

mm(['a.js', 'b.md', 'c.txt'], '!*.{js,txt}');
//=> ['b.md']
mm(['a.md', 'b.js', 'c.txt', 'd.json'], ['*.*', '!*.{js,txt}']);
//=> ['a.md', 'd.json']

Switch from minimatch

Use micromatch.isMatch() instead of minimatch()


The main minimatch() function returns true/false for a single file path and pattern:

var minimatch = require('minimatch');
minimatch('foo.js', '*.js');
//=> 'true'


Use .isMatch() to get the same result:

var mm = require('micromatch');
mm.isMatch('foo.js', '*.js');
//=> 'true'

This implementation difference is necessary since the main micromatch() method supports matching on multiple globs, with behavior similar to multimatch.


var mm = require('micromatch');


mm.isMatch(filepath, globPattern);

Returns true if a file path matches the given glob pattern.


mm.isMatch('.verb.md', '*.md');
//=> false
mm.isMatch('.verb.md', '*.md', {dot: true});
//=> true


Returns true if any part of a file path match the given glob pattern. Think of this is "has path" versus "is path".


.isMatch() would return false for both of the following:

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


Returns a function for matching using the supplied pattern. e.g. create your own "matcher". The advantage of this method is that the pattern can be compiled outside of a loop.


Can be any of the following:

  • glob/string
  • regex
  • function


var isMatch = mm.matcher('*.md');
var files = [];
['a.md', 'b.txt', 'c.md'].forEach(function(fp) {
  if (isMatch(fp)) {


Returns a function that can be passed to Array#filter().


  • patterns {String|Array}:


Single glob:

var fn = mm.filter('*.md');
['a.js', 'b.txt', 'c.md'].filter(fn);
//=> ['c.md']
var fn = mm.filter('[a-c]');
['a', 'b', 'c', 'd', 'e'].filter(fn);
//=> ['a', 'b', 'c']

Array of glob patterns:

var arr = [1,2,3,4,5,6,7,8,9,10,11,12,13,14,15];
var fn = mm.filter(['{1..10}', '![7-9]', '!{3..4}']);
//=> [1, 2, 5, 6, 10]

(Internally this function generates the matching function using the [matcher] method. You can use the [matcher] method directly to create your own filter function)


Returns true if a file path matches any of the given patterns.

mm.any(filepath, patterns, options);


  • filepath {String}: The file path to test.
  • patterns {String|Array}: One or more glob patterns
  • options: {Object}: options to pass to the .matcher() method.


mm.any('abc', ['!*z']);
//=> true
mm.any('abc', ['a*', 'z*']);
//=> true
mm.any('abc', 'a*');
//=> true
mm.any('abc', ['z*']);
//=> false


Returns an object with a regex-compatible string and tokens.

// when `track` is enabled (for debugging), the `history` array is used
// to record each mutation to the glob pattern as it's converted to regex
{ options: { track: false, dot: undefined, makeRe: true, negated: false },
  pattern: '(.*\\/|^)bar\\/(?:(?!(?:^|\\/)\\.).)*?',
  history: [],
   { path:
      { whole: '**/bar/**',
        dirname: '**/bar/',
        filename: '**',
        basename: '**',
        extname: '',
        ext: '' },
      { glob: true,
        negated: false,
        globstar: true,
        dotfile: false,
        dotdir: false },
     match: {},
     original: '**/bar/**',
     pattern: '**/bar/**',
     base: '' } }


Create a regular expression for matching file paths based on the given pattern:

//=> /^(?:(?!\.)(?=.)[^/]*?\.js)$/


All options should work the same way as minimatch.


Match dotfiles.

Type: {Boolean}

Default: false


Allow glob patterns without slashes to match a file path based on its basename.

Type: {Boolean}

Default: false


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


Don't expand braces in glob patterns.

Type: {Boolean}

Default: false


Use a case-insensitive regex for matching files.

Type: {Boolean}

Default: false


If true, when no matches are found the actual (array-ified) glob pattern is returned instead of an empty array.

Type: {Boolean}

Default: false


Cache the platform (e.g. win32) to prevent this from being looked up for every fil.

Type: {Boolean}

Default: true

Other features

Micromatch also supports the following.

Extended globbing

Extended globbing as described by the bash man page:

| pattern | regex equivalent | description | | --- | --- | | ?(pattern-list) | (...|...)? | Matches zero or one occurrence of the given patterns | | *(pattern-list) | (...|...)* | Matches zero or more occurrences of the given patterns | | +(pattern-list) | (...|...)+ | Matches one or more occurrences of the given patterns | | @(pattern-list) | (...|...) * | Matches one of the given patterns | | !(pattern-list) | N/A | Matches anything except one of the given patterns |

* @ isn't a RegEx character.

Brace Expansion

In simple cases, brace expansion appears to work the same way as the logical OR operator. For example, (a|b) will achieve the same result as {a,b}.

Here are some powerful features unique to brace expansion (versus character classes):

  • range expansion: a{1..3}b/*.js expands to: ['a1b/*.js', 'a2b/*.js', 'a3b/*.js']
  • nesting: a{c,{d,e}}b/*.js expands to: ['acb/*.js', 'adb/*.js', 'aeb/*.js']

Learn about brace expansion, or visit braces to ask questions and create an issue related to brace-expansion, or to see the full range of features and options related to brace expansion.

Regex character classes

With the exception of brace expansion ({a,b}, {1..5}, etc), most of the special characters convert directly to regex, so you can expect them to follow the same rules and produce the same results as regex.

For example, 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']
  • [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, parenthese can be nested, so patterns like ((a|b)|c)/b will work. But it might be easier to achieve your goal using brace expansion.


Run the benchmarks:

npm run benchmark

As of March 06, 2015:

#1: basename-braces.js 
  micromatch.js x 25,776 ops/sec ±0.68% (98 runs sampled)
  minimatch.js x 3,335 ops/sec ±1.09% (98 runs sampled)
#2: basename.js 
  micromatch.js x 24,676 ops/sec ±0.56% (95 runs sampled)
  minimatch.js x 4,908 ops/sec ±0.95% (97 runs sampled)
#3: braces-no-glob.js 
  micromatch.js x 473,492 ops/sec ±0.64% (96 runs sampled)
  minimatch.js x 27,705 ops/sec ±1.78% (91 runs sampled)
#4: braces.js 
  micromatch.js x 42,522 ops/sec ±0.63% (97 runs sampled)
  minimatch.js x 3,995 ops/sec ±1.36% (95 runs sampled)
#5: immediate.js 
  micromatch.js x 24,048 ops/sec ±0.72% (95 runs sampled)
  minimatch.js x 4,786 ops/sec ±1.40% (95 runs sampled)
#6: large.js 
  micromatch.js x 773 ops/sec ±0.62% (98 runs sampled)
  minimatch.js x 27.52 ops/sec ±0.66% (49 runs sampled)
#7: long.js 
  micromatch.js x 7,388 ops/sec ±0.64% (99 runs sampled)
  minimatch.js x 608 ops/sec ±0.95% (95 runs sampled)
#8: mid.js 
  micromatch.js x 41,193 ops/sec ±0.74% (99 runs sampled)
  minimatch.js x 2,724 ops/sec ±1.09% (97 runs sampled)
#9: multi-patterns.js 
  micromatch.js x 12,909 ops/sec ±0.71% (93 runs sampled)
  minimatch.js x 2,798 ops/sec ±1.45% (95 runs sampled)
#10: no-glob.js 
  micromatch.js x 430,787 ops/sec ±0.66% (98 runs sampled)
  minimatch.js x 47,222 ops/sec ±2.19% (86 runs sampled)
#11: range.js 
  micromatch.js x 474,561 ops/sec ±0.69% (97 runs sampled)
  minimatch.js x 10,819 ops/sec ±2.20% (88 runs sampled)
#12: shallow.js 
  micromatch.js x 239,098 ops/sec ±0.67% (96 runs sampled)
  minimatch.js x 27,782 ops/sec ±2.12% (92 runs sampled)
#13: short.js 
  micromatch.js x 707,905 ops/sec ±0.97% (97 runs sampled)
  minimatch.js x 52,171 ops/sec ±2.45% (84 runs sampled)

Run tests

Install dev dependencies.

npm i -d && npm test


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

Please be sure to run the benchmarks before/after any code changes to judge the impact before you do a PR. thanks!


  • braces: Fastest brace expansion for node.js, with the most complete support for the Bash 4.3 braces specification.
  • fill-range: Fill in a range of numbers or letters, optionally passing an increment or multiplier to use.
  • expand-range: Fast, bash-like range expansion. Expand a range of numbers or letters, uppercase or lowercase. See the benchmarks. Used by micromatch.
  • parse-glob: Parse a glob pattern into an object of tokens.
  • is-glob: Returns true if the given string looks like a glob pattern.


Jon Schlinkert


Copyright (c) 2014-2015 Jon Schlinkert
Released under the MIT license

This file was generated by verb-cli on March 06, 2015.


npm i [email protected]





Last publish


  • avatar
  • avatar
  • avatar