OptionalallowOptionalbracemax number of {...} patterns to expand. Default 100_000.
Optionaldebugprint LOTS of debugging output
Optionaldotallow matches that start with . even if the pattern does not
Optionalflipinvert the results of negated matches
Optionalmagicalconsider braces to be "magic" for the purpose of hasMagic
OptionalmatchIf 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.
OptionalmaxMax depth to traverse for nested extglobs like *(a|b|c)
Default is 2, which is quite low, but any higher value swiftly results in punishing performance impacts. Note that this is not relevant when the globstar types can be safely coalesced into a single set.
For example, *(a|@(b|c)|d) would be flattened into
*(a|b|c|d). Thus, many common extglobs will retain good
performance and never hit this limit, even if they are
excessively deep and complicated.
If the limit is hit, then the extglob characters are simply
not parsed, and the pattern effectively switches into
noextglob: true mode for the contents of that nested
sub-pattern. This will typically not result in a match,
but is considered a valid trade-off for security and
performance.
OptionalmaxMax number of non-adjacent ** patterns to recursively walk down.
The default of 200 is almost certainly high enough for most purposes, and can handle absurdly excessive patterns.
Optionalnobracedo not expand {x,y} style braces
Optionalnocaseignore case
Optionalnocaseignore case only in wildcard patterns
Optionalnocommentdo not treat patterns starting with # as a comment
Optionalnoextdo not expand extglobs like +(a|b)
Optionalnoglobstartreat ** the same as *
Optionalnonegatedo not treat patterns starting with ! as a negation
Optionalnonullreturn the pattern if nothing matches
OptionaloptimizationA number indicating the level of optimization that should be done to the pattern prior to parsing and using it for matches.
OptionalpartialCompare 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.
Optionalplatformoperating system platform
Optionalpreservedo not collapse multiple / into a single /
OptionalwindowsWhen a pattern starts with a UNC path or drive letter, and in
nocase:true mode, do not convert the root portions of the
pattern into a case-insensitive regular expression, and instead
leave them as strings.
This is the default when the platform is win32 and
nocase:true is set.
Optionalwindowstreat \\ as a path separator, not an escape character
inverse of MinimatchOptions.windowsPathsNoEscape