Upgrading braces from 2.x to 3.x
Comparison of the public API of braces 2.3.2 and 3.0.3, 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 | 2 |
| Changed class or interface members | 1 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 1 |
| New exports | 1 |
Removed exports
None detected.
Changed signatures
None detected.
Removed class or interface members
| member | import | Before |
|---|---|---|
Options.optimize | braces | boolean | undefined |
Options.unescape | braces | boolean | undefined |
Changed class or interface members
| member | Before | After |
|---|---|---|
Options.transform | ((str: string) => string) | undefined | Transform | undefined |
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
| Before | After | |
|---|---|---|
engines.node | >=0.10.0 | >=8 |
New exports (1)
| import | export | kind |
|---|---|---|
braces | Transform | type |
Frequently asked questions
What are the breaking changes when upgrading braces from 2 to 3?
Between braces 2.3.2 and 3.0.3, Vigia found 0 removed exports, 0 changed signatures and 3 removed or changed class or interface members.
What became deprecated in braces 3?
0 exports or members are newly marked as deprecated in braces 3.0.3.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/braces/upgrade?from=2.3.2&to=3.0.3