Displaying 1 to 11 from 11 results

parent-module - Get the path of the parent module

  •    Javascript

Node.js exposes module.parent, but it only gives you the first cached parent, which is not necessarily the actual parent.By default it will return the path of the immediate parent.

stackman - He is like Batman, but for Node.js stack traces

  •    Javascript

Give Stackman an error and he will give an array of stack frames with extremely detailed information for each frame in the stack trace.With Stackman you get access to the actual source code and surrounding lines for where the error occurred, you get to know if it happened inside a 3rd party module, in Node.js or in your own code. For a full list of information, check out the API below.

traceback - Easy access to the call stack, for Node.js


Writing a Node app? Need to know the function backtrace? Don't want to compile C++ code? Use Traceback. Traceback provides a normal JavaScript array of the execution stack frames. You can see function names, line numbers, and other useful stuff.

clarify - Remove nodecore related stack trace noise

  •    Javascript

To active require clarify. The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

coffeestack - CoffeeScript Stacktrace Converter

  •    CoffeeScript

Module to convert JavaScript stack traces to CoffeeScript stack traces.

stackinfo - Gets an object containing normalized stacktrace information across browsers.

  •    Javascript

Gets an object containing normalized stacktrace information across browsers. If you want to programmatically inspect the stack, this is the module for you. This uses stacktrace.js to get stack traces. stackinfo([<exception>]) - returns stack trace information in the below format. If <exception> is passed, the stacktrace will be taken from that exception, otherwise a stacktrace will be generated for the current call. Passed exceptions doesn't work in IE or Safari 5 (this is a limitation of stacktrace.js).

node-superstack - long stack traces for node.js

  •    Javascript

Your stack traces will now extend beyond async call boundaries. From the code above. We have no idea which setTimeout call actually caused the error.