Stricter detection of Node Buffer in browser environment

[rosssteytler]

It seems that in a browser environment, anything defined as Buffer on the window object, even if it's not a complete buffer implementation, causes the library to crash.

Relevant code:

const Buffer = typeof globalThis === 'object' && globalThis.Buffer;
const hasNodeBuffer = typeof Buffer !== 'undefined'
const ByteArrayAllocate = hasNodeBuffer ? Buffer.allocUnsafeSlow : Uint8Array

https://github.com/kriszyp/cbor-x/blob/master/encode.js#L8

In my case, window.Buffer contains a Buffer implementation which doesn't support allocUnsafeSlow, but this could be any definition of Buffer, such as window.Buffer = {}. I don't have the option to remove the Buffer definition from the global scope.

A possible solution might be to perform stricter checks on globalThis.Buffer to ensure allocUnsafeSlow exists before using it. Alternatively, it may be safer to introduce an option to explicitly disable the Node.js Buffer usage, which could be enabled or disabled in browser environments.