Find a way to read blobs synchronously

[jcbhmr]

No description provided.

[jcbhmr]

looks like the trick of expecting pull(cb) to run synchronously only works sometimes

[jcbhmr]

so this doesn't work https://github.com/jcbhmr/fileapi/blob/3500f6071e6a438bb39661c2d997b9bcfa9d6cc3/src/readBlobAsArrayBufferSync.ts

instead, i guess we could use synckit and transfer it to a worker thread, wait for the result, then transfer back an arraybuffer, right?

[jcbhmr]

turns out synckit doesn't support transferList: un-ts/synckit#131

instead, I guess the best bet is to fork it into @jcbhmr/synckit or something

[jcbhmr]

btw for that introspective nodejs magic internal stuff, here's some important bits:

https://github.com/nodejs/node/blob/e7618fb5a5fc25d76b6474e2a6607f04fd6f10e0/lib/internal/blob.js#L265-L294

https://github.com/nodejs/node/blob/86a8335a0604cae534ceb4a832070c4a351f3fde/src/node_blob.cc#L331-L370

[jcbhmr]

ok so if i can get the transferring and serialization magic to work, this COULD work? unless... i don't want the blob to be completely serialized when it passes the worker-barrier, I just want the REF to be passed, not the data COPIED to the other worker... hmmm

[jcbhmr]

looking at this it doesnt LOOK like the underlying bytes are copied

[JounQin]

turns out synckit doesn't support transferList: un-ts/synckit#131

instead, I guess the best bet is to fork it into @jcbhmr/synckit or something

Hi, I think if there's a good use case for it, a PR is better?