Upgrading base64-js from 0.x to 1.x
Comparison of the public API of base64-js 0.0.8 and 1.5.1, 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 | 1 |
Removed exports
None detected.
Changed signatures
| export | Before | After |
|---|---|---|
base64-js · toByteArray | (encoded: string): Uint8Array<ArrayBufferLike> | (b64: string): Uint8Array<ArrayBufferLike> |
base64-js · fromByteArray | (bytes: Uint8Array<ArrayBufferLike>): string | (uint8: Uint8Array<ArrayBufferLike>): string |
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.4 | — |
New exports (1)
| import | export | kind |
|---|---|---|
base64-js | byteLength | function |
Frequently asked questions
What are the breaking changes when upgrading base64-js from 0 to 1?
Between base64-js 0.0.8 and 1.5.1, Vigia found 0 removed exports, 2 changed signatures and 0 removed or changed class or interface members.
What became deprecated in base64-js 1?
0 exports or members are newly marked as deprecated in base64-js 1.5.1.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/base64-js/upgrade?from=0.0.8&to=1.5.1