Matteo Collina

> Well if someone more knowledgeable than me about AWS can guarantee it doesn't effect production that's at least a silver lining Yes. It's well documented: https://docs.aws.amazon.com/lambda/latest/dg/lambda-concurrency.html.

Thanks for reporting! Would you like to send a Pull Request to address this issue? Remember to add unit tests.

This is as at odds with devs wanting _less_ modules in production, and there is no way to achieve boths.

I don't know how to help with this, it's a matter of letting the module find its binary.

It’s not a good idea to remove node stream support. For Node.js client and server side usage, we need them to have decent performance. Moreover we need the bl module...

> Does using WebStreams instead of readable-stream in browsers have any benefits? Bundle size would be significantly lower.

> Ok so why not doing this on readable-stream package instead? I don't understand the question. WebStreams and Node.js streams have incompatible APIs and semantics.

> About the switch from Buffer to UInt8Array are you +1 or not We can't, due to how `bl` works.

I don't really understand what the benefit of that would be, the goal of bl is to implement the API of Buffer over a list of buffers.

What I mean is that it's 100% out of scope for bl, because that exposes the `Buffer` API and aims to be compatible with `Buffer`. Therefore you'd need an equivalent...