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).
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.
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).Under non-browser engines (Node.js, React Native, etc.) a full polyfill is used as those platforms do not provide sufficiently complete / non-buggy
TextDecoderAPIs.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.jsimport.