Uppy VS filepond

This is hand-wavey, but that can't be true: less complex type systems manage to express all kinds of interfaces correctly all the time.

You're asking me to tell on my coworkers, and I'm too loyal to throw them under the bus :)

Well, OK, here's one, but I'll keep it as blameless as possible. We had a thing where we wanted to register some event handlers. The primary use of these event handlers was to run a selector, and if the selected data changed, trigger an update, passing the selected data along. The initial implementation used existential types to store a list of callbacks, each returning different selected data. The "driver" then did the equality checking and update triggering. We later changed this, so that the callbacks - as far as the driver was concerned - all returned `void`, eliminating the need for an existential type. We just had to move the equality checking and update triggering inside the callbacks.

Some features are straightforward translations: anywhere you have overloading and/or optional arguments you can (and often should) simplify by refactoring into multiple functions.

For a concrete, public example...well, I remember the Uppy library had a lot of stuff like this. A lot of work goes into making it's "Plugin" interface look the way it does (start at [1] and keep reading I guess), and while I haven't sat down and re-engineered it I don't think it needs to be this way, if you're willing to give up some of the slickness of the interface.

[1] https://github.com/transloadit/uppy/blob/main/packages/%40up...

Look at https://uppy.io/ open source and lot of integrations. You can keep moving to different levels of abstraction as required and see some good practices of how things are done.

I just found uppy. This will be the next one I use. https://uppy.io/

I’m building a photo sharing website and want to make it incredibly easy to upload photos. Of course I could just utilize AWS official packages but that’s pretty bare bones. I could also use next-s3-upload which is purpose built for Next and simplifies some things but is still fairly basic. But then there’s things like uppy that provides everything you’d ever need in an uploaded (third party sources, camera, etc.) that would be nice to haves, but apparently doesn’t play well with Next without a separate Node server.

Media file uploads with the Uppy JavaScript uploader plugin

Check out Uppy and Uppy Companion: https://github.com/transloadit/uppy/

I would look at Uppy.js, I've used it in an enterprise application and it works super well, makes it super easy to do what you're trying to achieve with progress bars for each file.

I started to try out https://uppy.io/ but their lack of good documentation makes my life a bit difficult. However, uppy seems to be the only available solution out there in the React land (i dont want to implement it by myself).

FilePond: Simplify file uploads with FilePond

Have a look at https://pqina.nl/filepond/

Just looking at the docs for react-dropzone, they recommend Filepond for something similar to what you're looking for.

Just two example libraries: FilePond, DropZone

I've had this problem for a while. I'm using filepond on the frontend for uploading files, and I've followed their setup documentation, but I cannot for the life of me get it to work. I'm using django-drf-filepond as the backend for my FilePond uploads, but I keep getting `Bad Request: /uploads/process/` errors. My FilePond configuration is

GitHub - pqina/filepond: 🌊 A flexible and fun JavaScript file upload library

This works as intended if the form does not invoke filepond.