Upgrading binary-extensions from 2.x to 3.x
Comparison of the public API of binary-extensions 2.3.0 and 3.2.0, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.
Summary
| Removed import paths | 1 |
|---|---|
| Removed exports | 0 |
| Changed signatures | 0 |
| 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 import paths
| Removed import paths |
|---|
binary-extensions/binary-extensions.json |
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)
| Before | After | |
|---|---|---|
engines.node | >=8 | >=18.20 |
New exports (1)
| import | export | kind |
|---|---|---|
binary-extensions | default | variable |
Frequently asked questions
What are the breaking changes when upgrading binary-extensions from 2 to 3?
Between binary-extensions 2.3.0 and 3.2.0, Vigia found 0 removed exports, 0 changed signatures and 0 removed or changed class or interface members.
What became deprecated in binary-extensions 3?
0 exports or members are newly marked as deprecated in binary-extensions 3.2.0.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/binary-extensions/upgrade?from=2.3.0&to=3.2.0