When deleting cache on Server Side, Uppy's implement of TUS JS Client throws 404 and show console

[BlinqxRobbieMinderhoud]

Initial checklist

• I understand this is a bug report and questions should be posted in the Community Forum
• I searched issues and couldn’t find anything (or linked relevant results below)

Link to runnable example

No response

Steps to reproduce

Uppy Version: v4.3.0

Simply uploading a file will cause this error.

My setup:

This happens after the file is fully uploaded. This is stored in a function that complete the upload.

Afterwards I will get a 404 error regarding the cache key that is not found.

This may be a problem in the tus js client.

Expected behavior

A warning in my console or an option that will catch the console error instead of throwing it in my console.

Actual behavior

a 404 error in my console

[Murderlon]

Hi, this seems like a problem with your chosen tus server, not with tus-js-client nor Uppy.

[BlinqxRobbieMinderhoud]

I might have to agree with you on this one. I doubted where it should go. Because the js client could handle it in a different way. Or the server should have an option not to throw this.

One thing I am considering though, is that it may be good to have some functionality when it comes to handling these errors. If I for example have a custom error messaging in Javascript, I may want to display that using my custom solution instead of console errors.

What do you think? Could we add something to enable this custom kind of handling instead of throwing it out in the console?