ArrayBuffer views should be recognized as binary data and treated respectively

[Gozala]

At the moment Uint8Array (or any other view of ArrayBuffer seems to be treated as array of numbers)

js-ipld-dag-cbor/src/util.js

Lines 37 to 48 in 5d3389a

	function transform (obj) {
	if (!obj || Buffer.isBuffer(obj) || typeof obj === 'string') {
	return obj
	}
	if (Array.isArray(obj)) {
	return obj.map(transform)
	}
	if (CID.isCID(obj)) {
	return tagCID(obj)
	}

This causes issues when things are moved across the message channel, because even fields that were Buffer's come up as Uint8Arrays on the other end. For this reason I would like to propose a change which would treat Uint8Array (and I'm inclined to suggest other ArrayBuffer views as well) as a binary data instead (same as Buffers is treated today).

It is worth pointing out that ArrayBuffer itself will appear as {byteLength:number} which I don't think is ideal, but probably out of scope.

[vmx]

Fixed by #129.

[Gozala]

@vmx who's going to publish to npm ? I need to propagate thes into js-ipfs to be able to integrate into ipfs/js-ipfs#3081.

Would you mind posting here or in the mentioned pull once it's makes to npm so I can propagate ?

[vmx]

I already published it right away, it's v0.15.3.