Packages

@exodus/bytes

1.16.0 · 22 Sep 2026MIT78.5M / weekRepositorynpmAtom feed

Your version

20 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.

  1. 1.16.0

    22 Sep 2026
    • crc32

  2. 1.15.2

    21 Sep 2026
    • fromHex on Node.js validation in 47fc52c

    • Node.js 25+ is not affected.

    • Browsers and other non-"node" import conditions are not affected.

  3. 1.15.1

    20 May 2026
    • Don't use bigint literals

  4. 1.15.0

    4 Mar 2026
    • isomorphicDecode(), isomorphicEncode() in /encoding.js (in #68)

    • fromBase32crockford / toBase32crockford in /base32.js

    • typedCopyBytes() in /array.js

  5. 1.14.1

    13 Feb 2026

    fix: ensure TextEncoder never returns pooled arrays

  6. 1.14.0

    12 Feb 2026
    • Fix makeBase58check() Typescript types

    • Add sideEffects configuration

      Only @exodus/bytes/encoding.js export has side-effects, and those side-effects are internal:

      It is documented to load multi-byte codecs for both this import and future (and previous) /encoding-lite.js imports, even if the current import does not use the provided TextDecoder.

      Both /encoding.js and /encoding-lite.js are designed to return the exact same TextDecoder class and methods, and loading full implementation provides multi-byte encodings support everywhere.

      As /encoding-lite.js can be used as a global polyfill, the setup has to avoid polyfill conflicts if something loads /encoding.js and then something else replaces it with /encoding-lite.js (or vice versa)

      The same mechanism is reused to keep /whatwg.js minimal by default, and only support multi-byte encodings if /encoding.js was imported and loaded them at any point.

      This is not a new change, just documenting the existing behavior and exposing sideEffects configuration so that bundlers can optmize out other imports.

    • Further bundle size optimizations

  7. 1.13.0

    11 Feb 2026
    • Bundle size reductions, especially for browsers

      Under browser module resolution target, we rely on browsers to have a working UTF-8 / UTF-16 / windows-1252 (latin1 subset) TextDecoder implementation that doesn't have bugs when used without streaming and with ignoreBOM: true, and a TextEncoder

      While browsers have bugs even in UTF-8, those bugs are related to streams and/or BOM processing, and that specific combination we use seems to be always robust.

      In previous versions we already used native codepaths for those where possible and operated under the same assumption.

    • Disable hex/base64 performance optimization for Firefox >=133 <146

      We used a guarded useragent check for those versions to prefer js fallback instead of native base64 / hex implementations, as native was slow before FF 146 (ref: bugzilla.mozilla.org/show_bug.cgi and linked issues)

      As the usage of FF <146 diminished according to caniuse stats, this check is not worth it anymore.

      This version removes that useragent check.

      Those Firefox versions are still supported by the library, but now the native base64 / hex implementation is always used when available.

      See 8cab29a for implementation details.

  8. 1.12.0

    8 Feb 2026
    • Fix UTF-16 on platforms with present but broken native UTF-16 TextDecoder (e.g. workerd, see #6028)

    • Test in CI on workerd, xs and graaljs

  9. 1.11.0

    1 Feb 2026
    • Add /whatwg.js and percentEncodeAfterEncoding()

    • utf16toStringLoose(Uint16Array) on Big-Endian hardware

  10. 1.10.0

    26 Jan 2026
    • Add TypeScript types for all entry points

    • Test and accept Uint8Array<SharedArrayBuffer> input

    • Add iso-2022-jp fatal encoder (in #36)

  11. 1.9.0

    18 Jan 2026
    • Implement strict multi-byte encoders, except for iso-2022-jp for now

    • Add /encoding-browser.js to load only native lightweight TextDecoder/TextEncoder in browser bundles

    • Add /index.js export with usage warning, mostly for IDEs

  12. 1.8.0

    2 Jan 2026
    • Support iso-8859-1, iso-8859-9, iso-8859-11 encodings in single-byte.js

    • latin1fromString, latin1toString

    • Types for encoding.js

  13. 1.7.0

    28 Dec 2025
    • Implement TextDecoderStream / TextEncoderStream
      Requires Streams to be either supported by the platform or polyfilled

    • Implement createSinglebyteEncoder (only fatal mode for now)

    • Fix a missing check for non-Latin1 chars in fromBech32 / fromBech32m on non-Hermes barebone engines
      Node.js, browsers, other non-barebones and Hermes / React Native were not affected

  14. 1.6.0

    25 Dec 2025

    TextDecoder performance improvements for non-Unicode encodings.

  15. 1.5.0

    24 Dec 2025
    • Support cross-context Uint8Array instances in new TextEncoder().encodeInto(...)

    • Faster legacy multi-byte decoders

  16. 1.4.0

    24 Dec 2025
    • Add support for cross-context ArrayBuffer in TextDecoder

    • /wif.js now does not need @exodus/crypto peer dependency when used on Node.js

  17. 1.3.0

    23 Dec 2025
  18. 1.2.0

    22 Dec 2025

    Add support for Node.js builds without ICU in /utf-8.js and TextDecoder implementation.

  19. 1.0.0 – 1.1.02 releases without a noteShow each

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.