Tim Kevin Oxley
Tim Kevin Oxley
Oh wow ok I've just spent far too long trying to figure out *how* Jest was even seeing the error it was reporting. Really could do with jest saying *something*,...
@JoeLangewayClear's workaround will suppress these errors, but it's kind of like disabling the _engine fault_ light in your car and claiming you "fixed it" 
This issue seems related to https://github.com/facebook/jest/issues/5958
> When I replace the uncaught function with the below, my tests pass, and my app works just fine. Sure, though this makes all uncaught rejections into acceptable behaviour, but...
@wmertens ah that's an issue as well, jest replacing your own handlers
 @bcoe Was there a meeting about this? What was the outcome? It looks like support was added in `action-semantic-pull-request` but I don't see any mention of multiple scopes in...
Ok, I found an ugly workaround that just rewrites the `error.message` property instead of creating a new `Error`. One downside is that if the error's `.stack` getter has already been...
@tarohi24 You're right, this does seem like a duplicate. I'll let a team member close this in hopes it will refresh their memory first.
+1 please publish to npm
@seejohnrun Hiverness changed his username, repo is still up: https://github.com/ovaillancourt/hashlib