graphql-upload-minimal VS sharp

Using the latest version of graphql-upload with NestJS can be quite tricky since it uses mjs, this means we need to use dynamic imports, alternative you can use graphql-upload-minimal, or graphql-upload version 13.

Sharp Documentation: Link

ESLint does an amazing job in detecting floating promises. I've not had it miss one, ever. When adding this to a project, I've discovered multiple accidental bugs due to a missing "await" keyword--bugs that were extremely subtle and intermittent in many cases.

The only thing it can't do is determine that you actually did handle the promise later. Which is fine. It's a LINTING RULE, and false positives are the name of the game.

What's BAD is when you accidentally miss handling a promise at all. It's an invisible error without the linting rule.

Your other comments...don't even make sense. You're going to build a Lanczos filter by hand? Or you're only going to ... compile ImageMagick to WebAssembly?!, ... an implementation which is tremendously slower (nearly unusably so for large images) than that of Sharp:

https://www.npmjs.com/package/sharp

... which is simply an import away?

No, what you're doing is called "motivated reasoning." You've concluded that Deno is the best, and you're reinterpreting all of my complaints in convoluted ways to support your predetermined conclusion.

Standard fanboy behavior. Or troll behavior. I cite Poe's Law as why it's impossible to tell the difference.

sharp - An image processing library

To actually edit the images, we are going to use sharp. Sharp is a high-performance image processing library. You can do all the cool things we want to do with it. Install the library then import it with import sharp from 'sharp'.

2. sharp

I've run this on a few SBCs (single board computers). A Raspberry Pi Zero 2W is adequate for the job. The demo is running on a OrangePi Lite2, which is nominally more powerful, but not as well supported, software-wise. Compiling the image procesing software (sharp) under Ambian was pretty hit and miss, whereas on Raspbian it is plug and play.

For 1, and 2, the possibility is there. If https://sharp.pixelplumbing.com/ support it, we can convert the file to those formats. It can be a setting from the user to set which format of the generated thumbnail files to be stored as

Now that we have the path, we can use sharp to read the width and height of the image.