Upgrading micromatch from 3.x to 4.x
Comparison of the public API of micromatch 3.1.10 and 4.0.8, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.
Summary
| Removed import paths | 0 |
|---|---|
| Removed exports | 0 |
| Changed signatures | 0 |
| Removed class or interface members | 7 |
| Changed class or interface members | 0 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 1 |
| New exports | 6 |
Removed exports
None detected.
Changed signatures
None detected.
Removed class or interface members
| member | import | Before |
|---|---|---|
Options.cache | micromatch | boolean | undefined |
Options.nonull | micromatch | boolean | undefined |
Options.nodupes | micromatch | boolean | undefined |
Options.unixify | micromatch | boolean | undefined |
Options.nullglob | micromatch | boolean | undefined |
Options.sourcemap | micromatch | boolean | undefined |
Options.snapdragon | micromatch | object | undefined |
Changed class or interface members
None detected.
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
| Before | After | |
|---|---|---|
engines.node | >=0.10.0 | >=8.6 |
New exports (6)
| import | export | kind |
|---|---|---|
micromatch | Item | interface |
micromatch | ScanInfo | interface |
micromatch | ScanOptions | interface |
micromatch | ScanInfoToken | interface |
micromatch | ScanInfoWithParts | interface |
micromatch | ScanInfoWithTokens | interface |
Frequently asked questions
What are the breaking changes when upgrading micromatch from 3 to 4?
Between micromatch 3.1.10 and 4.0.8, Vigia found 0 removed exports, 0 changed signatures and 7 removed or changed class or interface members.
What became deprecated in micromatch 4?
0 exports or members are newly marked as deprecated in micromatch 4.0.8.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/micromatch/upgrade?from=3.1.10&to=4.0.8