Getting at the raw trace about longjohn HOT 1 OPEN

Hey Jeremy,

Sorry for being so behind on this!

This is an unfortunate suggestion, but try using https://github.com/felixge/node-stack-trace in order to parse the stack trace for now. I was trying to figure out a way to expose both the raw trace and the stringified trace through the same error object but have yet to figure out a good way to do this. The basic issue is that adding a property to the error object that gets returned out seemed to not be possible in the way that I did things. In essence, the prepareStackTrace method can only be called once for any error. You could take a look in there and see if you can get the raw stack attached to the error that gets returned out.

Also, if you'd like something like currentStack, you could use visionmedia's https://github.com/visionmedia/callsite to get a stacktrace. He had another lib that does exactly what you want based on callsite, but I forget what it is now.

from longjohn.