Grégory Horion

any update on this @killix ?

OMG! I wasted so much time on this! Please update the doc 🙏

well, it's not only about running commands. I'm not sure that people would want to reveal the environment variables of the running process.

you guys should check out: https://github.com/miratronix/s3-readable-stream

it's crazy how much time code is spent in the try/catch - would be much more efficient to rely on `DDP._CurrentMethodInvocation.get() || DDP._CurrentPublicationInvocation.get();`

Thanks @zimme - Not a blocker, will try to find some time for this :)

Isn't `rawBody(file.createReadStream())` going to load the all file into memory though? ...

> @gregory Yep, that's true. Ideally we'd just forward the stream to `form-data`, but as mentioned above in my code comment, there's a bug that prevents this currently. My solution...

You got it right @mike-marcacci that's the issue. That's why I [exposed a new option](https://github.com/jaydenseric/graphql-upload/pull/168/files#diff-4bc221396721e80a53576c01d8dbf4ccR341) in jaydenseric/graphql-upload#168 , to allow any other library relying on the file size & file...

I don't think that's an issue @mike-marcacci as you'll usually set those manually: ```js // data needs to be specified explicitly in this case. form.append('file', buffer, { filename: file.filename, contentType:...