longjohn / 0.2.4 last updated a year ago created on Jul 2nd 2012
Install
npm install --save longjohn
Clone
git clone git@github.com:mattinsler/longjohn.git
dependencies
No dependencies listed.
maintainers
versions
10 total
| 0.2.4 | a year ago | mattinsler |
| 0.2.3 | a year ago | mattinsler |
| 0.2.2 | a year ago | mattinsler |
| 0.2.1 | 2 years ago | mattinsler |
| 0.2.0 | 2 years ago | mattinsler |
| 0.0.5 | 2 years ago | mattinsler |
| 0.0.4 | 2 years ago | mattinsler |
| 0.0.3 | 3 years ago | mattinsler |
| 0.0.2 | 3 years ago | mattinsler |
| 0.0.1 | 3 years ago | mattinsler |
readme
longjohn
Long stack traces for node.js with configurable call trace length
Inspiration
I wrote this while trying to add long-stack-traces to my server and realizing that there were issues with support of EventEmitter::removeListener. The node HTTP Server will begin to leak callbacks and any of your own code that relies on removing listeners would not work as anticipated.
So what to do... I stole the code and rewrote it. I've added support for removeListener along with the ability to cut off the number of async calls the library will trace. I hope you like it!
Please thank tlrobinson for the initial implementation!
Production Use
Longjohn collects a large amount of data in order to provide useful stack traces. While it is very helpful in development and testing environments, it is not recommended to use longjohn in production. The data collection puts a lot of strain on V8's garbage collector and can greatly slow down heavily-loaded applications.
Installation
Just npm install it!
Usage
To use longjohn, require it in your code (probably in some initialization code). That's all!