micromatch
4.0.8 · 23 Aug 2024MIT222.4M / weekRepositorynpmAtom feed
69 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
- 4.x · latest line
4.0.8
23 Aug 2024Ultimate release that fixes both CVE-2024-4067 and CVE-2024-4068. We consider the issues low-priority, so even if you see automated scanners saying otherwise, don't be scared.
4.0.7
22 May 2024- Security
It is vulnerable to CVE-2024-4067
- Security
Updated braces to v3.0.3 to avoid CVE-2024-4068
This is basically v4.0.5, with some README updates
This is basically v4.0.5, with some README updates
- Security
It is vulnerable to CVE-2024-4067
- Security
Updated braces to v3.0.3 to avoid CVE-2024-4068
Does NOT break API compatibility
4.0.6
21 May 2024- Security
Fixes CVE-2024-4067
Added
hasBracesto check if a pattern contains braces.BREAKS API COMPATIBILITY
Added
hasBracesto check if a pattern contains braces.- Security
Fixes CVE-2024-4067
BREAKS API COMPATIBILITY
Should be labeled as a major release, but it's not.
4.0.5
24 Mar 20224.0.3
9 Apr 2021Enforce newer version of picomatch with bugfixes
4.0.0
10 Apr 2019- Breaking
Require Node.js >= 8.6
- Breaking
Removed support for passing an array of brace patterns to
micromatch.braces(). - Breaking
To strictly enforce closing brackets (for
{,[, and(), you must now usestrictBrackets=trueinstead ofstrictErrors.
Added
Adds support for
options.onMatch. See the readme for detailsAdds support for
options.onIgnore. See the readme for detailsAdds support for
options.onResult. See the readme for details
Breaking changes
- Breaking
Require Node.js >= 8.6
- Breaking
Removed support for passing an array of brace patterns to
micromatch.braces(). - Breaking
To strictly enforce closing brackets (for
{,[, and(), you must now usestrictBrackets=trueinstead ofstrictErrors. - Breaking
cache- caching and all related options and methods have been removed - Breaking
options.unixifywas renamed tooptions.windows - Breaking
options.nodupesWas removed. Duplicates are always removed by default. You can override this with custom behavior by using theonMatch,onResultandonIgnorefunctions. - Breaking
options.snapdragonwas removed, as snapdragon is no longer used. - Breaking
options.sourcemapwas removed, as snapdragon is no longer used, which provided sourcemap support.
- 3.x
3.0.1 – 3.1.1016 releases without a noteShow each
- 3.1.1022 Mar 2018no note
- 3.1.924 Feb 2018no note
- 3.1.820 Feb 2018no note
- 3.1.720 Feb 2018no note
- 3.1.618 Feb 2018no note
- 3.1.58 Jan 2018no note
- 3.1.430 Oct 2017no note
- 3.1.321 Oct 2017no note
- 3.1.221 Oct 2017no note
- 3.1.121 Oct 2017no note
- 3.1.011 Sep 2017no note
- 3.0.58 Sep 2017no note
- 3.0.411 Jul 2017no note
- 3.0.32 Jun 2017no note
- 3.0.231 May 2017no note
- 3.0.129 May 2017no note
3.0.0
29 May 2017Micromatch results are directly compared to bash results
In rare cases, when micromatch and bash disagree, micromatch's results are compared to minimatch's results
Micromatch is much more accurate than minimatch, so there were cases where I had to make assumptions. I'll try to document these.
Complete overhaul, with 36,000+ new unit tests validated against actual output generated by Bash and minimatch. More specifically, 35,000+ of the tests:
Micromatch results are directly compared to bash results
In rare cases, when micromatch and bash disagree, micromatch's results are compared to minimatch's results
Micromatch is much more accurate than minimatch, so there were cases where I had to make assumptions. I'll try to document these.
This refactor introduces a parser and compiler that are supersets of more granular parsers and compilers from other sub-modules. Each of these sub-modules has a singular responsibility and focuses on a certain type of matching that aligns with a specific part of the Bash "expansion" API.
These sub-modules work like plugins to seamlessly create the micromatch parser/compiler, so that strings are parsed in one pass, an AST is created, then a new string is generated by the compiler.
Here are those sub-modules with links to related prs on those modules if you want to see how they contribute to this code:
nanomatch (new library) - glob expansion (
*,**,?and[...])) braces - brace expansion ({1..10},{a,b,c}, etc) extglob - extended globs (!(a|b),@(!(foo|bar)), etc) expand-brackets - POSIX character classes[[:alpha:][:digit:]]Added
Source map support (optionally created when using parse or compile - I have no idea what the use case is yet, but they come for free) (note that source maps are not generated for brace expansion at present, since the braces compiler uses a different strategy. I'll update if/when this changes).
Parser is exposed, so that implementors can customize or override specific micromatch parsers if necessary
Compiler is exposed, so that implementors can customize or override specific micromatch compilers if necessary
Fixed
Even safer - micromatch has always generated optimized patterns so it's not subject to DoS exploits like minimatch (completely different than the regex DoS issue, minimatch and multimatch are still openly exposed to being used for DoS attacks), but more safeguards were built into this refactor
Changed
The public API of this library did not change in this version and should be safe to upgrade without changing implentor code. However, we have released this as a major version for the following reasons:
out of an abundance of caution due to the large amount of code changed in this release
we have improved parser accuracy to such a degree that some implementors using invalid globs have noted change in behavior. If this is the case for you, please check that you are using a valid glob expression before logging a bug with this library
- 2.x
2.3.6
19 Dec 2015Also linting and other minor formatting
- 1.x
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.