Catching errors from other things

[zackify]

The .catch from one ajax call is catching errors completely unrelated. One time I had required a file that did not exist, and it was being caught inside a module that I was making an ajax request in using axios. Promises seem to be messed up.

[Nicolab]

Here also. Axios catch an Exception generated by a Chrome extension

[zackify]

Glad I'm not the only one, I don't get how more people aren't seeing this.

[Nicolab]

May be because an exception is thrown into the then() method.
In my case in the then() method I have an events dispatcher and the Chrome extension explain the Flow.

[Nicolab]

Hmm, Axios even catch exceptions thrown out of the method then().

[mzabriskie]

This is definitely not expected behavior. For those experiencing this, can you please provide a gist, or some example how to reproduce? Thanks.

[csm123]

I'm using the same sort of promises as Axios on a project, and the promise catches exceptions in then. That is, exceptions in then don't throw an error in the Chrome console - instead the promise has the error. You can tack on .catch(function(err) { console.error(err); }); for debug purposes, but that's not really a lasting solution. Unsure of what to do here.

[csm123]

Related: stefanpenner/es6-promise#40

[csm123]

Also, this is how it's handled in es6-promise's parent library, RSVP.

https://github.com/tildeio/rsvp.js#error-handling

[dmt0]

I'm getting this in one (but not all) of my projects. Any time I hit an undefined.member in the render() function of any React component, Axios catches it.

##199

[nickuraltsev]

This issue is not actionable as is. Please provide a code snippet that reproduces the problem and reopen.

[dmt0]

According to this it's actually the correct behavior apparently.

[gee1k]

I am also getting this error. Is there an explanation for this?