Yunong Xiao

The require.paths problems is due to node 0.6.x Rolling back node on your system to 0.4.x will fix that issue. I suggest using https://github.com/creationix/nvm to manage various node versions on...

:+1: This would be a really great way to enable the use of other tools and provide additional functionality.

@kelapure This doesn't mean mdb_v8 isn't working. It could be because your Node application isn't doing anything. If there's nothing active, then all you'll see on the stack is just...

+1000 On Fri, Feb 9, 2018 at 11:15 AM David Pacheco wrote: > findjsobjects -r is useful for finding which objects reference a > particular object. However, it doesn't find...

@swills The test suite and lint/style checkers are run via `npm test`. Thanks for the patch!

Makes sense that this is a bug. It should respect the body size.

Interesting. Can you please give me some sample code I can run to repro?

Hi, so this actually happens when an exception is thrown asynchronously like so: ``` js exports.asyncThrow = function (t) { setImmediate(function() { throw new Error('thrown asynchronously');}); } ``` Running the...

Turns out github created a new issue when i submitted my PR, it's under #245 With the patch, functions thrown asynchronously now print their stacks like so: ``` sh └─[0]...

@caolan Can we merge this patch?