James M Snell

There is a challenge here since given that the structured clone algorithm doesn't handle custom Error objects well without losing data. Some platforms that might not be able to handle...

In node.js we implement a custom value serializer delegate that allows us to serialize and deserialize host objects. The key challenge is that those have to be backed in the...

Just an update on this... we recently just landed early support for this in Node.js. When sending an `AbortSignal` over postMessage, a new `AbortSignal` is created on the receiving end...

Yeah, the transferable bit is temporary. I expect to have that fixed in the coming few weeks On Sat, Dec 18, 2021, 19:38 James Browning ***@***.***> wrote: > Just an...

Couple of options there: 1. Calling `formData()` can assume that the content is multipart/form-data, rejecting the promise only if it cannot be successfully parsed as such, or... 2. The `formData()`...

ah right, forgot about that `boundary` parameter on the content-type. In that case, we either do as you suggest and limit it to `new Response(stream, { headers }).formData()` or allow...

> What should happen if you call releaseLock() while arrayBuffer() is still pending, and then you acquire a new reader? I think in that case we'd have no choice but...

> Succinctness alone is not a compelling argument in my opinion, because the new reader mode is more verbose than using new Response: No, definitely not the only argument. The...

Definite +1 to a `finally` algorithm on the transformer.

Yeah, it definitely limits some of the interaction with the `Event` object but I think for the use cases this is intended for, that's likely ok? And where those are...