Packages

micromatch

4.0.8 · 23 Aug 2024MIT222.4M / weekRepositorynpmAtom feed

Upgrading micromatch From 2.3.11 to 3.0.0

1 release in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 2.3.11Clears its advisory, Latest4.0.8
The note of 3.0.0 lists no breaking change or deprecation, which is rare for a major.
  1. 2.3.11yours
  2. 3.0.0target
?
changes to make
0
advisories fixed
0
new
0
fixes

Security

1 advisory still affects 3.0.0

Upgrading to 4.0.8 clears it.

9 other lines we could not sort, mostly version bumps
  • Micromatch results are directly compared to bash results

    3.0.0
  • In rare cases, when micromatch and bash disagree, micromatch's results are compared to minimatch's results

    3.0.0
  • Micromatch is much more accurate than minimatch, so there were cases where I had to make assumptions. I'll try to document these.

    3.0.0
  • 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).

    3.0.0
  • Parser is exposed, so that implementors can customize or override specific micromatch parsers if necessary

    3.0.0
  • Compiler is exposed, so that implementors can customize or override specific micromatch compilers if necessary

    3.0.0
  • 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

    3.0.0
  • Out of an abundance of caution due to the large amount of code changed in this release

    3.0.0
  • 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

    3.0.0

1 internal line (docs, tests, tooling) left out.

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.