Develop

Hm. I'm torn on this.

On one hand, I totally agree it's nice to know why something isn't working -- but at the same time -- this is a tradeoff.

If stormpath ever goes down, or there is an outage of some sort -- should the entire site stop functioning and throw errors? I dunno.

Since this library is handling all of these errors internally, it doesn't really make sense to me to go out of the way to expose the errors to the developer -- their code is not touching that at all.