Vigia

Upgrading brace-expansion from 4.x to 5.x

Comparison of the public API of brace-expansion 4.0.1 and 5.0.12, 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 signatures0
Removed class or interface members0
Changed class or interface members0
Newly deprecated0
Requirement changes (engines, peer dependencies)1
New exports6

Removed exports

None detected.

Changed signatures

None detected.

Removed class or interface members

None detected.

Changed class or interface members

None detected.

Newly deprecated

None detected.

Requirement changes (engines, peer dependencies)

BeforeAfter
engines.node>= 1820 || >=22
New exports (6)
importexportkind
brace-expansionexpandfunction
brace-expansionEXPANSION_MAXvariable
brace-expansionEXPANSION_MAX_DEPTHvariable
brace-expansionEXPANSION_MAX_LENGTHvariable
brace-expansionBraceExpansionOptionstype
brace-expansionEXPANSION_MAX_REWRITESvariable

Frequently asked questions

What are the breaking changes when upgrading brace-expansion from 4 to 5?

Between brace-expansion 4.0.1 and 5.0.12, Vigia found 0 removed exports, 0 changed signatures and 0 removed or changed class or interface members.

What became deprecated in brace-expansion 5?

0 exports or members are newly marked as deprecated in brace-expansion 5.0.12.

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/brace-expansion/upgrade?from=4.0.1&to=5.0.12