Michael Hart

Which documentation? It's not mandatory for sigv4 signing alone – but some services use it (eg, S3). Most services don't though.

Expose how? Sorry, can you explain what you're trying to do? You can set this header yourself and aws4fetch should continue to work fine (in fact, it will use it...

Where are you running this? As the README says, this is "for environments that support fetch and SubtleCrypto"

Which Node.js version? Which OS? Sent from Gmail Mobile On Mon, 29 Jan 2024 at 7:30 pm, Dibo ***@***.***> wrote: > AwsClient > > in a Nodejs app which supports...

Not sure what's wrong with your env – it's defined for me: ``` $ node Welcome to Node.js v20.11.0. Type ".help" for more information. > typeof crypto 'object' ```

I'm still seeing this behaviour with the latest version (1.0.11) on node v0.10.11 - with at least one module anyway (https://github.com/rvagg/node-levelup). ie - there's no output. It works fine with...

Forget my last comment, wrapping the stream using `new Readable().wrap(stream)` seems to make it all work.

Hey hey! Hmmm. Here's what you'd need to change: https://github.com/mhart/ts-eager/blob/87a7c3bd1bae0eb312286e0172f891ce026c7dd8/register.js#L100 I guess that could be exposed somehow – I wonder how common it is to do what you're doing?

I was looking at this too – there's one unfortunate downside to esbuild being a separate process which is that `require` needs to resolve synchronously – so each compilation ends...

Yeah, I wasn't trying to suggest it was esbuild's responsibility in any way – kinda surprised after all this time that Node.js doesn't have better sync primitives for communicating with...