trycatch icon indicating copy to clipboard operation
trycatch copied to clipboard

An asynchronous domain-based exception handler with long stack traces for node.js

Results 9 trycatch issues
Sort by recently updated
recently updated
newest added

Bumps [lodash](https://github.com/lodash/lodash) from 2.4.2 to 4.17.19. Release notes Sourced from lodash's releases. 4.17.16 4.0.0 lodash v4.0.0 2015 was big year! Lodash became the most depended on npm package, passed 1...

dependencies

Hi When we use inheritance for error handling, but also for standard error class like ReferenceError etc..., the stack trace is lost. Its because of function isError in formatError.js check...

I am still using this puppy... and I am still an happy customer. I was looking at the implementation of the long stack traces. It looks like that you do...

An opt-in `Promise` API is the best avenue for adding finally support. Likely, the callback API will be deprecated at a point that makes sense and avoids as much inconvenience...

We've been trying to track down a memory leak which has been killing our prod boxes. Eventually, with the help of the heapdump module, we've been led to believe that...

FWIW. My workaround/hack mentioned in https://github.com/CrabDude/trycatch/issues/45.

There are 4 parts to trycatch: - Fixing callback context (EE handlers at time of listen vs at construction) - Guarding core from userland errors and fixing - Long-stack-traces -...

And Error.create for convenience. Something like... ``` javascript trycatch(function() { ... }, [EvalError], function(err) { // only catch EvalError }) ```