@exodus/bytes
    Preparing search index...

    Module @exodus/bytes/encoding-browser.js

    Same as @exodus/bytes/encoding.js, but in browsers instead of polyfilling just uses whatever the browser provides, drastically reducing the bundle size (to less than 2 KiB gzipped).

    import { TextDecoder, TextEncoder } from '@exodus/bytes/encoding-browser.js'
    import { TextDecoderStream, TextEncoderStream } from '@exodus/bytes/encoding-browser.js' // Requires Streams

    // Hooks for standards
    import { getBOMEncoding, legacyHookDecode, labelToName, normalizeEncoding } from '@exodus/bytes/encoding-browser.js'

    Under non-browser engines (Node.js, React Native, etc.) a full polyfill is used as those platforms do not provide sufficiently complete / non-buggy TextDecoder APIs.

    Note

    Implementations in browsers have bugs, but they are fixing them and the expected update window is short.
    If you want to circumvent browser bugs, use full @exodus/bytes/encoding.js import.

    References

    getBOMEncoding → getBOMEncoding
    labelToName → labelToName
    legacyHookDecode → legacyHookDecode
    normalizeEncoding → normalizeEncoding
    TextDecoder → TextDecoder
    TextDecoderStream → TextDecoderStream
    TextEncoder → TextEncoder
    TextEncoderStream → TextEncoderStream