Upgrading picomatch from 3.x to 4.x
Comparison of the public API of picomatch 3.0.2 and 4.0.7, 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 | 6 |
| Changed class or interface members | 0 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 1 |
| New exports | 0 |
Removed exports
None detected.
Changed signatures
None detected.
Removed class or interface members
| member | import | Before |
|---|---|---|
PicomatchOptions.cwd | picomatch | string | undefined |
PicomatchOptions.nodupes | picomatch | boolean | undefined |
PicomatchOptions.failglob | picomatch | boolean | undefined |
PicomatchOptions.lookbehinds | picomatch | boolean | undefined |
PicomatchOptions.posixSlashes | picomatch | boolean | undefined |
PicomatchOptions.noquantifiers | picomatch | boolean | undefined |
Changed class or interface members
None detected.
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
| Before | After | |
|---|---|---|
engines.node | >=10 | >=12 |
Frequently asked questions
What are the breaking changes when upgrading picomatch from 3 to 4?
Between picomatch 3.0.2 and 4.0.7, Vigia found 0 removed exports, 0 changed signatures and 6 removed or changed class or interface members.
What became deprecated in picomatch 4?
0 exports or members are newly marked as deprecated in picomatch 4.0.7.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/picomatch/upgrade?from=3.0.2&to=4.0.7