feat(adapter-fetch): Add support for handling binary data

[offirgolan]

Description

Add support for handling binary data.

Motivation and Context

#183

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I have added tests to cover my changes.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• My code follows the code style of this project.
• My commits and the title of this PR follow the Conventional Commits Specification.
• I have read the contributing guidelines.

[jasonmit]

to-arraybuffer uses require('buffer').Buffer so I'm confused how this all is built in our current build pipeline - is it some how "browserifying" the node implementation and also bundling the npm "buffer" package?

[offirgolan]

Ok so looked more into it to see what was actually being built. We current have rollup-plugin-node-builtins setup which has support for using Buffer via buffer-es6.

If I imported the buffer via import { Buffer } from 'buffer' it only inlines the polyfill for the UMD build but when I used from 'buffer/', it inlined it for all 3 builds (CJS, ES, and UMD). Since this is only meant for the browser, it would make sense for it to be be polyfilled in all 3.

[jasonmit]

Explains a lot, was very confused - thanks for looking into it

[offirgolan]

This dist is EOL and is no longer supported by Chrome. That was the reason for the failing builds.