Upgrading balanced-match from 3.x to 4.x
Comparison of the public API of balanced-match 3.0.1 and 4.0.4, 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 | 2 |
| Changed signatures | 1 |
| Removed class or interface members | 0 |
| Changed class or interface members | 0 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 1 |
| New exports | 1 |
Removed exports
| import | export | kind | Before |
|---|---|---|---|
balanced-match | Output | interface | interface |
balanced-match | default | function | (a: string | RegExp, b: string | RegExp, str: string): Output | undefined |
Changed signatures
| export | Before | After |
|---|---|---|
balanced-match · range | (a: string | RegExp, b: string | RegExp, str: string): [number, number] | undefined | (a: string, b: string, str: string): [number, number] | undefined |
Removed class or interface members
None detected.
Changed class or interface members
None detected.
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
| Before | After | |
|---|---|---|
engines.node | >= 16 | 18 || 20 || >=22 |
New exports (1)
| import | export | kind |
|---|---|---|
balanced-match | balanced | variable |
Frequently asked questions
What are the breaking changes when upgrading balanced-match from 3 to 4?
Between balanced-match 3.0.1 and 4.0.4, Vigia found 2 removed exports, 1 changed signatures and 0 removed or changed class or interface members.
What became deprecated in balanced-match 4?
0 exports or members are newly marked as deprecated in balanced-match 4.0.4.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/balanced-match/upgrade?from=3.0.1&to=4.0.4