Use streams in write property operation on browsers

[relu91]

I've created this issue mostly to monitor the two issues that I linked below.

After plumbing into the inner workings of broserify and the Web platform, I've found that sadly stream upload is not supported for browsers. This means that we can't use a stream to write properties or invoke actions. Solving this issue is going to be tricky but I hope to find a patch that will only be active on browser environments.

For the ones that are curious. Here are the relevant issues:
whatwg/fetch#1438
https://bugs.chromium.org/p/chromium/issues/detail?id=688906

Originally posted by @relu91 in #785 (comment)

[samubura]

I'm having issues using the browser bundle to invoke actions
the error I get is:

TypeError: stream_1.Readable.from is not a function
valueToContent https://cdn.jsdelivr.net/npm/@node-wot/[email protected]/dist/wot-bundle.min.js:49981
invokeAction https://cdn.jsdelivr.net/npm/@node-wot/[email protected]/dist/wot-bundle.min.js:49762
__awaiter https://cdn.jsdelivr.net/npm/@node-wot/[email protected]/dist/wot-bundle.min.js:49326
__awaiter https://cdn.jsdelivr.net/npm/@node-wot/[email protected]/dist/wot-bundle.min.js:49322
invokeAction https://cdn.jsdelivr.net/npm/@node-wot/[email protected]/dist/wot-bundle.min.js:49747`

is this related to this issue?

[danielpeintner]

The 'stream_1.Readable.from is not a function' issue was resolved by #809.

This was done on 27 July and no more release has been published since than. I hope we can publish a new release soon. In the meantime you may want to use wot-bundle.min.js from a master build.

[relu91]

The new release is out, @samubura can you confirm that you don't experience that issue anymore?

[samubura]

Yes! I can confirm it is working as expected now.