Reading the exact error the browser reports

[ghost]

When using the API, I catch - obviously - errors with .catch(error).

The problem is that while in the browser I see a specific error message, catch reports a more generic error.

E.g: if I get in Chrome "request has been blocked by CORS policy", with catch I get "Request has been terminated, Possible causes: the network is offline, Origin is not allowed by Access-Control-Allow-Origin, the page is being unloaded, etc.".

Is there a way to read the specific error message from catch, i.e. from the error the API reports?

[kadamwhite]

This appears to be a function of how Superagent wraps error objects. I agree that it would be preferable to return a clearer error; this would represent a BC break so I'll add a note to the 2.0 milestone to audit our transport methods for return error clarity.