You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hmm, wondering if not we should try to fix the real problem that is that we return a custom AbortError message, it should rather be a DOMException
// Browser test:ctrl=newAbortController()ctrl.abort()fetch('/',ctrl).catch(console.log)// DOMException { // name: AbortError,// code: 20,// message: "Failed to execute 'fetch' on 'Window': The user aborted a request." // }
We could optionally start to depend on node-domexception. it's already included by another sub dependency of ours (fetch-blob).
Hmm, wondering if not we should try to fix the real problem that is that we return a custom AbortError message, it should rather be a
DOMException
We could optionally start to depend on node-domexception. it's already included by another sub dependency of ours (fetch-blob).
Originally posted by @jimmywarting in #1513 (comment)
The text was updated successfully, but these errors were encountered: