Rik

maybe `onaddfile` callback, first param is an error if something went wrong, could then auto-remove?

Maybe try `onaddfilestart` but note that you can only know the size of file/blob objects, so if user drops a URL there's no way to block at that point

appreciate the PR will review when I have some time

Hi Jake, Thanks for the detailed report. The transforms are happening in canvas, and as this runs in the main thread it is blocking for UI interactions. WebKit based browsers...

Hm, that should indeed be similar, but types where added after those plugins so might be some inconstancy. I'd advise to `@ts-ignore` this for now.

Currently, the field name is the same so the server doesn't need to know which metadata is attached. This is an interesting approach, I will give this some thought.

@juongithub I'll mark this as an enhancement. It's currently low priority as you can define a custom processing method. It should then be fairly easy to also send the metadata...

Use this method: https://pqina.nl/filepond/docs/patterns/api/server/#process-1 ```js FilePond.setOptions({ server: { process:(fieldName, file, metadata, load, error, progress, abort, transfer, options) => { // fieldName is the name of the input field // file...

Do you mean grouping them under one item?

I'm not sure I understand the issue, can you create a test case on codesandbox.io that would be very helpful.