Adam Crabtree

I'll take a look.

Unfortunately, I don't anticipate being able to work on this anytime in the near future.

It's actually totally possible, but a little more invasive than try catch already is. Effectively, you would need to track all Errors in Error.prepareStackTrace, and then filter for unhandledRejection errors....

This would be implemented in [`lib/trycatch.js`](https://github.com/CrabDude/trycatch/blob/master/lib/trycatch.js). Off the top of my head, the way `unhandledRejection` works presently is that for every promise exception, it adds an asynchronous check for whether...

I'll do this sometime soon since I'm working on my own company now.

Oh fun. First, **thanks for all the work you've done here.** `trycatch` is complex, and memory leaks even more so. So, this is basically an asynchronous [stack overflow](https://en.wikipedia.org/wiki/Stack_overflow), and so...

I'm honestly trying to think of a short-term solution for you, but there really isn't one. Your fix is the your best option since the async catch nesting isn't necessarily...

Looks like `WeakMap` is supported without a flag in v0.12, which is promising, because it precludes the need for the tradeoff (removing domains before an alternative exists).

I appreciate you working with me to reach a solution. You're a model user / contributor. ;) I think there's definitely a solution here using WeakMap (I know you concluded...

For more complex workflows like mocha, I would recommend foregoing the utility that is `babel-node-debug` and opt instead for the more manually workflow: 1. Follow the [Babel setup](https://babeljs.io/docs/setup/#mocha) for use...