Trying not to loose stream data on "Input buffer contains unsupported image format" about sharp HOT 4 CLOSED

If you're generating multiple output images (dimensions and formats) from a single input and a local filesystem is available then my advice to use it, at least for the input, remains. This will both lower fragmentation and increase throughput.

from sharp.

tell sharp to just be a "PassThrough" if it can't support a file

sharp will always perform a decode/encode roundtrip.

The scenario you describe, where you need alternative logic depending on the contents of a Stream, suggests you'll either need to create your own Transform Stream or perhaps remove Streams entirely with something like https://github.com/stream-utils/raw-body

If this is for Strapi, please see strapi/strapi#16978 (comment)

from sharp.

Yes it's for strapi and I'm actually reworking the internals to read the stream directly from the request instead of having a file on disk.
Are you recommending not using streams as a general comment ? is it because in anycase you endup loading enverything into memory or sth like that ?

It might be valuable to know (or document) what operations (metadata,stats,resize,...) actually are buffering everything into memory and which actually benefit from streams 🤔

from sharp.

Going to close this as your answer is enough to know I will need to manage on our side anyway ;)

from sharp.