richarddavison

> Hi @richarddavison, are you already working on this issue? If you haven't already, would you give me the opportunity to work on it? Hi @nabetti1720! I'm not, please go...

Landed in https://github.com/awslabs/llrt/pull/360

Hi @jabrks. We want to support response streams but first we have to implement native streaming for performance reasons https://github.com/awslabs/llrt/issues/178

Thanks for the suggestion but we already have [a streams polyfill](https://github.com/awslabs/llrt/blob/main/src/js/stream.ts) but that won't perform as well as we desire due to lack of a JIT. Basically every byte that...

Hi @nocquidant. So you wan't fetch to route request via a proxy configured via HTTP(s)_PROXY? How would you configure auth? Meanwhile, can you use something like s_client to work around...

Thanks, we will add this!

> Hi @richarddavison do we have any ETAs on the crypto implementation? I'm unable to migrate my codebase to LLRT because I'm blocked due to SubtleCrypto and RSA. Hi @ShivamJoker!...

Thanks for the detailed report! Yes, we can provide a versions table of the LLRT version and QuickJS version. Maybe also async-runtime (`tokio`) version!

Fantastic, thanks for the PR! Reading `tokio` & `qjs` versions would require some gymnastics in build.rs to parse cargo.toml and and rquickjs submodule. I think it's a lot of work...

Hi 👋. That’s a very good question. There are a couple of reasons why Hermes wasn’t used: - It only supports ES6 (not fully) - It’s mainly built for ahead...