Allow patterns to match filenames starting with a period, even if the pattern does not explicitly have a period in that spot.
Note that by default, 'a/**' + '/b' will not match a/.d/b, unless dot is set.
Returns from negate expressions the same as if they were not negated. (Ie, true on a hit, false on a miss.)
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.
Do not expand {a,b} and {1..3} brace sets.
Perform a case-insensitive match.
Suppress the behavior of treating # at the start of a pattern as a comment.
Disable "extglob" style patterns like +(a|b).
Disable ** matching against multiple folder names.
Suppress the behavior of treating a leading ! character as negation.
When a match is not found by minimatch.match,
return a list containing the pattern itself if this option is set.
Otherwise, an empty list is returned if there are no matches.
Compare a partial path to a pattern. As long as the parts of the path that are present are not contradicted by the pattern, it will be treated as a match. This is useful in applications where you're walking through a folder structure, and don't yet have the full path, but want to ensure that you do not walk down paths that can never be a match.
Use \\ as a path separator only, and never as an escape
character. If set, all \\ characters are replaced with / in
the pattern. Note that this makes it impossible to match
against paths containing literal glob pattern characters, but
allows matching with patterns constructed using path.join() and
path.resolve() on Windows platforms, mimicking the (buggy!)
behavior of earlier versions on Windows. Please use with
caution, and be mindful of the caveat about Windows paths
For legacy reasons, this is also set if
options.allowWindowsEscape is set to the exact value false.
Dump a ton of stuff to stderr.
false