Rik

Thanks for reporting, this indeed looks like a bug.

Ah yes, forgot to reopen after the update.

I think this might've been a temporary issue because it seems to be back online now. Yes, see update here: https://status.render.com > Unresolved incident: Intermittent 503 errors for services.

I'm not sure, handling of small and large files is the same, is it perhaps possible the server is not returning progress updates?

I've got these kinds of functions and it tree shaking seems to stop the callbacks from working. Open to suggestions. ```js const createFoo = () => { return { onsomething:...

Alright, I'll test it later this week or at the start of the next

@thisconnect I ran some more tests. The `ondragend` handler will be set by another function. When treeshaking is enabled, Rollup will remove `api.ondragend(position)`, this will cause FilePond to stop working....

We require the issue template to be filled out on all new issues. The issue template helps us collect all the information we need to address your submission efficiently. The...

Thanks, good to know, I’m looking to switch to GitHub issue forms to make this more strict. Please understand that every single day devs open zero effort issues, the only...

Currently the FilePond item status doesn't wrap, so the only option would be to make sure the filepond container doesn't get this small. Hope to address this in a future...