Upgrading bytes from 2.x to 3.x
Comparison of the public API of bytes 2.5.0 and 3.1.2, 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 | 2 |
| Removed class or interface members | 0 |
| Changed class or interface members | 0 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 1 |
| New exports | 2 |
Removed exports
None detected.
Changed signatures
| export | Before | After |
|---|---|---|
bytes · parse | (value: number): number | (value: string): number | (value: string | number): number | null |
bytes · format | (value: number, options?: BytesOptions | undefined): string | (value: number, options?: BytesOptions | undefined): string | null |
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 | >= 0.6 | >= 0.8 |
New exports (2)
| import | export | kind |
|---|---|---|
bytes | Unit | type |
bytes | BytesOptions | interface |
Frequently asked questions
What are the breaking changes when upgrading bytes from 2 to 3?
Between bytes 2.5.0 and 3.1.2, Vigia found 0 removed exports, 2 changed signatures and 0 removed or changed class or interface members.
What became deprecated in bytes 3?
0 exports or members are newly marked as deprecated in bytes 3.1.2.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/bytes/upgrade?from=2.5.0&to=3.1.2