multer VS busboy

Some basic examples of popular packages in the Javascript community include Express (a framework for building server applications) and Multer (a middleware for handling file uploads). These packages, when integrated into your project, can significantly streamline your development process.

Here are the docs for multer

You could use multipart/form-data https://github.com/expressjs/multer

multer - Middleware for Express.js to handle file uploads

busboy is what many Express middleware's such as multer use under the hood.

Maybe multer or validate-image-type?

🔀 Repositório no GitHub

Multer has some functions used to determine what type of file(s) to expect from the API request. Here we have used the 'multer.single("file")' function to let multer know that we're expecting a single file. (The full multer documentation can be found here).

You need something that can parse formData stuff. Like multer https://github.com/expressjs/multer

In this post we'll walk through the process of passing an image (or any file) to a Netlify function using FormData and busboy.

There is also bus boy or what I would do and that is look at WASM DuckDB, and then iterate through imported records and send over JSON.

This. If the file field happens to come before other fields, you have to do something with it before you get a chance to read the other fields because you can't rewind the stream (unless you write it somewhere). If you also control the frontend and can guarantee the order of the fields, you can use busboy like suggested but I'm guessing it's gonna be quite brittle.

I checked out StorageEngine and apparently , it will fix the problem with memory storage for thumbnail. But I also checked out Busboy which Multer is based on. and it looks like the File size limit functionality comes from Busboy. Like, multer get fileSize and passes it to Busboy and then busboy handles limiting the incoming data for all files. So I guess it is not possible to set multiple limit size from multer. Thanks

After digging through the source code of the package I found some tests that used exactly the approach that I needed by using the undocumented call busboy.write(request.body, function() {}); where I can pass-in the body data that we already have available in the Azure Function. This brought me to the following code. I log information about all the fields that we find, and I write, as a test, the files to disk in a temp folder to check if the server can process binary files correctly. When you run this same code in a Netlify function everything seems to work, but you will get crippled files!