Vigia

Upgrading minimatch from 9.x to 10.x

Comparison of the public API of minimatch 9.0.9 and 10.2.6, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.

Summary

Removed import paths0
Removed exports0
Changed signatures2
Removed class or interface members0
Changed class or interface members2
Newly deprecated1
Requirement changes (engines, peer dependencies)1
New exports2

Removed exports

None detected.

Changed signatures

exportBeforeAfter
minimatch · escape(s: string, { windowsPathsNoEscape, }?: Pick<MinimatchOptions, "windowsPathsNoEscape"> | undefined): string(s: string, { windowsPathsNoEscape, magicalBraces, }?: Pick<MinimatchOptions, "windowsPathsNoEscape" | "magicalBraces"> | undefined): string
minimatch · unescape(s: string, { windowsPathsNoEscape, }?: Pick<MinimatchOptions, "windowsPathsNoEscape"> | undefined): string(s: string, { windowsPathsNoEscape, magicalBraces, }?: Pick<MinimatchOptions, "windowsPathsNoEscape" | "magicalBraces"> | undefined): string

Removed class or interface members

None detected.

Changed class or interface members

memberBeforeAfter
AST.toJSON(): any[](): unknown[]
Minimatch.debug(..._: any[]): void(..._: unknown[]): void

Newly deprecated

export@deprecated
minimatch · MinimatchOptions.allowWindowsEscape—

Requirement changes (engines, peer dependencies)

BeforeAfter
engines.node>=16 || 14 >=14.1718 || 20 || >=22
New exports (2)
importexportkind
minimatchSeptype
minimatchPlatformtype

Frequently asked questions

What are the breaking changes when upgrading minimatch from 9 to 10?

Between minimatch 9.0.9 and 10.2.6, Vigia found 0 removed exports, 2 changed signatures and 2 removed or changed class or interface members.

What became deprecated in minimatch 10?

1 exports or members are newly marked as deprecated in minimatch 10.2.6.

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/minimatch/upgrade?from=9.0.9&to=10.2.6