{"_id":"coffee-backtrace","_rev":"25-4af93b9bd35e6729de44fa503ca36f63","name":"coffee-backtrace","description":"Expands coffee files in uncaught exceptions to add context with the compiled Javascript","dist-tags":{"latest":"0.3.5"},"versions":{"0.1.0":{"name":"coffee-backtrace","author":{"name":"Doug Patti","email":"douglas.patti@gmail.com"},"description":"Expands coffee files in uncaught exceptions to add context with the compiled Javascript","version":"0.1.0","repository":{"type":"git","url":"https://github.com/FogCreek/node-coffee-backtrace.git"},"main":"./lib/coffee-backtrace","keywords":["coffee","log","error","backtrace","debug"],"dependencies":{},"license":"MIT","readme":"# coffee-backtrace\n\nA Node.js module for servers written in CoffeeScript to aide in debugging\nuncaught exceptions.\n\n## What it does\n\nWhen an exception is thrown, unfortunately the error message and corresponding\nline number can be cryptic, as they correspond to what happened in the compiled\nJavaScript file, and not the source CoffeeScript file. This aims to reduce the\npain of debugging by finding the offending line and providing some context as\nwell. See some example output from the provided example file:\n\n```diff\n$ coffee example\nTypeError: Object #<Object> has no method 'getMessage'\n    at Object.Relay.speak [as _onTimeout] (/home/doug/dev/node-coffee-backtrace/example.coffee:13:40)\n>     }\n>\n>     Relay.prototype.speak = function() {\n>>      return process.stdout.write(this.getMessage() + '\\n');\n>     };\n>\n>     Relay.prototype.getMessage = function() {\n    at Timer.list.ontimeout (timers.js:101:19)\n```\n\nOf course, if you are using a terminal, the error is color-coded red to help it\nstand out more. The `>` are added so that the message is still able to be read\nin a log file.\n\n## How to use\n\n1. Add to your package.json dependencies or type `npm install coffee-backtrace`.\n\n2.  In your entry point file, add the following:\n\n    ```coffee\n    require('coffee-backtrace')\n    ```\n\n3. That's it.\n\n## Extra configuration\n\nYou can control the number of context lines shown in one of two ways:\n\n1. Start the process with the `COFFEE_BACKTRACE_CONTEXT` variable set:\n\n    ```sh\n    $ COFFEE_BACKTRACE_CONTEXT=10 coffee app.coffee\n    ```\n\n2. Use the `setContext` method on the required module:\n\n    ```coffee\n    require('coffee-backtrace').setContext(0)\n    ```\n","_id":"coffee-backtrace@0.1.0","dist":{"shasum":"78ff034871347f72faf27563799195a04e6654e4","tarball":"https://registry.npmjs.org/coffee-backtrace/-/coffee-backtrace-0.1.0.tgz","integrity":"sha512-Orw7G2Pq40O+Rx4LOA9RWFp839/F7e1+vaeGemM3WS8pELtja1i5aMsxfknYFvW+b8oHtLzex8ePdDFst8F1og==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIGPNsCVCo6kgNerwAad1oAkSYaLJCTy/UvCORzzfaXqCAiEAoKquPMQysnMrFi411IsH5TYTGt8ACXVGaBRX3k0RPPU="}]},"_npmVersion":"1.1.59","_npmUser":{"name":"dpatti","email":"douglas.patti@gmail.com"},"maintainers":[{"name":"dpatti","email":"douglas.patti@gmail.com"}]},"0.1.1":{"name":"coffee-backtrace","author":{"name":"Doug Patti","email":"douglas.patti@gmail.com"},"description":"Expands coffee files in uncaught exceptions to add context with the compiled Javascript","version":"0.1.1","repository":{"type":"git","url":"https://github.com/FogCreek/node-coffee-backtrace.git"},"main":"./lib/coffee-backtrace","keywords":["coffee","log","error","backtrace","debug"],"dependencies":{},"license":"MIT","readme":"# coffee-backtrace\n\nA Node.js module for servers written in CoffeeScript to aide in debugging\nuncaught exceptions.\n\n## What it does\n\nWhen an exception is thrown, unfortunately the error message and corresponding\nline number can be cryptic, as they correspond to what happened in the compiled\nJavaScript file, and not the source CoffeeScript file. This aims to reduce the\npain of debugging by finding the offending line and providing some context as\nwell. See some example output from the provided example file:\n\n```diff\n$ coffee example\nTypeError: Object #<Object> has no method 'getMessage'\n    at Object.Relay.speak [as _onTimeout] (/home/doug/dev/node-coffee-backtrace/example.coffee:13:40)\n>     }\n>\n>     Relay.prototype.speak = function() {\n>>      return process.stdout.write(this.getMessage() + '\\n');\n>     };\n>\n>     Relay.prototype.getMessage = function() {\n    at Timer.list.ontimeout (timers.js:101:19)\n```\n\nOf course, if you are using a terminal, the error is color-coded red to help it\nstand out more. The `>` are added so that the message is still able to be read\nin a log file.\n\n## How to use\n\n1. Add to your package.json dependencies and run `npm install` or run `npm install coffee-backtrace`.\n\n2.  In your entry point file, add the following:\n\n    ```coffee\n    require('coffee-backtrace')\n    ```\n\n3. That's it.\n\n## Extra configuration\n\nYou can control the number of context lines shown in one of two ways:\n\n1. Start the process with the `COFFEE_BACKTRACE_CONTEXT` variable set:\n\n    ```sh\n    $ COFFEE_BACKTRACE_CONTEXT=10 coffee app.coffee\n    ```\n\n2. Use the `setContext` method on the required module:\n\n    ```coffee\n    require('coffee-backtrace').setContext(0)\n    ```\n","_id":"coffee-backtrace@0.1.1","dist":{"shasum":"122f641e3ba74404f84dae6263be5b84ffae7ecd","tarball":"https://registry.npmjs.org/coffee-backtrace/-/coffee-backtrace-0.1.1.tgz","integrity":"sha512-RAu7irL93bh090fmggX9CHqmBEbxVwG+di0HLWIc6t6dw394CZMnVbWL22VYpmebihAmgkeXj4AdLp2c+7yeEA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIEBamzi0rbH99nu+f4a3JSLyCy06N9NMAeQ54rzQF+tdAiEA5pUgb9sPtXRLRYHoZYXtXYqoQBA46rwGrSQBGpuSAA4="}]},"_npmVersion":"1.1.59","_npmUser":{"name":"dpatti","email":"douglas.patti@gmail.com"},"maintainers":[{"name":"dpatti","email":"douglas.patti@gmail.com"}]},"0.1.2":{"name":"coffee-backtrace","author":{"name":"Doug Patti","email":"douglas.patti@gmail.com"},"description":"Expands coffee files in uncaught exceptions to add context with the compiled Javascript","version":"0.1.2","repository":{"type":"git","url":"https://github.com/FogCreek/node-coffee-backtrace.git"},"main":"./lib/coffee-backtrace","keywords":["coffee","log","error","backtrace","debug"],"dependencies":{},"license":"MIT","readme":"# coffee-backtrace\n\nA Node.js module for servers written in CoffeeScript to aide in debugging\nuncaught exceptions.\n\n## What it does\n\nWhen an exception is thrown, unfortunately the error message and corresponding\nline number can be cryptic, as they correspond to what happened in the compiled\nJavaScript file, and not the source CoffeeScript file. This aims to reduce the\npain of debugging by finding the offending line and providing some context as\nwell. See some example output from the provided example file:\n\n```diff\n$ coffee example\nTypeError: Object #<Object> has no method 'getMessage'\n    at Object.Relay.speak [as _onTimeout] (/home/doug/dev/node-coffee-backtrace/example.coffee:13:40)\n>     }\n>\n>     Relay.prototype.speak = function() {\n>>      return process.stdout.write(this.getMessage() + '\\n');\n>     };\n>\n>     Relay.prototype.getMessage = function() {\n    at Timer.list.ontimeout (timers.js:101:19)\n```\n\nOf course, if you are using a terminal, the error is color-coded red to help it\nstand out more. The `>` are added so that the message is still able to be read\nin a log file.\n\n## How to use\n\n1. Add to your package.json dependencies and run `npm install` or run `npm install coffee-backtrace`.\n\n2.  In your entry point file, add the following:\n\n    ```coffee\n    require('coffee-backtrace')\n    ```\n\n3. That's it.\n\n## Extra configuration\n\nYou can control the number of context lines shown in one of two ways:\n\n1. Start the process with the `COFFEE_BACKTRACE_CONTEXT` variable set:\n\n    ```sh\n    $ COFFEE_BACKTRACE_CONTEXT=10 coffee app.coffee\n    ```\n\n2. Use the `setContext` method on the required module:\n\n    ```coffee\n    require('coffee-backtrace').setContext(0)\n    ```\n","readmeFilename":"README.md","_id":"coffee-backtrace@0.1.2","dist":{"shasum":"26abc17f30fb4031a6e236d7f8b2f35c0515d0ff","tarball":"https://registry.npmjs.org/coffee-backtrace/-/coffee-backtrace-0.1.2.tgz","integrity":"sha512-c3t03gl7qEjd2JMFkn6TJqR0fd6IC3Eg9fY+WAJrfL77R0eQxGbD0OTLYhbR/2aHj7tsub6GzF3X+K4Bh/1W7g==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIHKzF+sTGwXLrQ9BOGAIojjW3Fgirw+UWdTkXbXqX+21AiBWkyW2UK7Z58Z2jRk16BLljziPgWAlo8CXoPHXIrupPg=="}]},"_from":".","_npmVersion":"1.2.14","_npmUser":{"name":"dpatti","email":"douglas.patti@gmail.com"},"maintainers":[{"name":"dpatti","email":"douglas.patti@gmail.com"}]},"0.2.0":{"name":"coffee-backtrace","author":{"name":"Doug Patti","email":"douglas.patti@gmail.com"},"description":"Expands coffee files in uncaught exceptions to add context with the compiled Javascript","version":"0.2.0","repository":{"type":"git","url":"https://github.com/FogCreek/node-coffee-backtrace.git"},"main":"./lib/coffee-backtrace","keywords":["coffee","log","error","backtrace","debug"],"dependencies":{},"license":"MIT","readme":"# coffee-backtrace\n\nA Node.js module for servers written in CoffeeScript to aide in debugging\nuncaught exceptions.\n\n**Note:** This package is somewhat redundant with CoffeeScript 1.6.2.\nCoffeeScript will now show you the *correct* line number of the exception within\nthe coffee file. However, CoffeeScript currently only performs this expansion on\nthe file executed with the command and not on any other required file. See [pull\nrequest 2968](https://github.com/jashkenas/coffee-script/pull/2968) for possible\ninformation regarding this being available on all files.\n\n## What it does\n\nWhen an exception is thrown, unfortunately the error message and corresponding\nline number can be cryptic, as they correspond to what happened in the compiled\nJavaScript file, and not the source CoffeeScript file. This aims to reduce the\npain of debugging by finding the offending line and providing some context as\nwell. See some example output from the provided example file:\n\n```\n$ coffee example.coffee\n\nTypeError: Object [object Object] has no method 'getMessage'\n at [object Object].Relay.speak [as _onTimeout] (/home/doug/dev/coffee-backtrace/example.coffee:12:40)\n         }\n\n         Relay.prototype.speak = function() {\n>          return process.stdout.write(this.getMessage() + '\\n');\n         };\n\n         Relay.prototype.getMessage = function() {\n at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)\n```\n\nOf course, if you are using a terminal, the error is color-coded red to help it\nstand out more. The `>` are added so that the message is still able to be read\nin a log file.\n\n## How to use\n\n1. Add to your package.json dependencies and run `npm install` or run `npm install coffee-backtrace`.\n\n2. In your entry point file, add the following:\n\n    ```coffee\n    require('coffee-backtrace')\n    ```\n\n3. That's it.\n\n## Extra configuration\n\nYou can control the number of context lines shown in one of two ways:\n\n1. Start the process with the `COFFEE_BACKTRACE_CONTEXT` variable set:\n\n    ```sh\n    $ COFFEE_BACKTRACE_CONTEXT=10 coffee app.coffee\n    ```\n\n2. Use the `setContext` method on the required module:\n\n    ```coffee\n    require('coffee-backtrace').setContext(0)\n    ```\n","readmeFilename":"README.md","_id":"coffee-backtrace@0.2.0","dist":{"shasum":"cb703df41cbcb1f7ad6a23b303a1bb0574f4301f","tarball":"https://registry.npmjs.org/coffee-backtrace/-/coffee-backtrace-0.2.0.tgz","integrity":"sha512-8y7SrT8mBKUp1zH+m75Y0U9n48fVkARfyPBysyBEXGJXBpwQiiabA9mtdToYION6WAihvC1DXlSTM8Yai9oviA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIDBkzd7RuM9nSCtMJx0b3v8qXnknFQlsQlsgNB1U0lH2AiAs6fb8yKKIPPvjC5rX9t6xynwLbREMlxp4FnVW9uvbjg=="}]},"_from":".","_npmVersion":"1.2.12","_npmUser":{"name":"dpatti","email":"douglas.patti@gmail.com"},"maintainers":[{"name":"dpatti","email":"douglas.patti@gmail.com"}]},"0.2.1":{"name":"coffee-backtrace","author":{"name":"Doug Patti","email":"douglas.patti@gmail.com"},"description":"Expands coffee files in uncaught exceptions to add context with the compiled Javascript","version":"0.2.1","repository":{"type":"git","url":"https://github.com/FogCreek/node-coffee-backtrace.git"},"main":"./lib/coffee-backtrace","keywords":["coffee","log","error","backtrace","debug"],"dependencies":{},"license":"MIT","readme":"# coffee-backtrace\n\nA Node.js module for servers written in CoffeeScript to aide in debugging\nuncaught exceptions.\n\n**Note:** This package is somewhat redundant with CoffeeScript 1.6.2.\nCoffeeScript will now show you the *correct* line number of the exception within\nthe coffee file. However, CoffeeScript currently only performs this expansion on\nthe file executed with the command and not on any other required file. See [pull\nrequest 2968](https://github.com/jashkenas/coffee-script/pull/2968) for possible\ninformation regarding this being available on all files.\n\n## What it does\n\nWhen an exception is thrown, unfortunately the error message and corresponding\nline number can be cryptic, as they correspond to what happened in the compiled\nJavaScript file, and not the source CoffeeScript file. This aims to reduce the\npain of debugging by finding the offending line and providing some context as\nwell. See some example output from the provided example file:\n\n```\n$ coffee example.coffee\n\nTypeError: Object [object Object] has no method 'getMessage'\n at [object Object].Relay.speak [as _onTimeout] (/home/doug/dev/coffee-backtrace/example.coffee:12:40)\n         }\n\n         Relay.prototype.speak = function() {\n>          return process.stdout.write(this.getMessage() + '\\n');\n         };\n\n         Relay.prototype.getMessage = function() {\n at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)\n```\n\nOf course, if you are using a terminal, the error is color-coded red to help it\nstand out more. The `>` are added so that the message is still able to be read\nin a log file.\n\n## How to use\n\n1. Add to your package.json dependencies and run `npm install` or run `npm install coffee-backtrace`.\n\n2. In your entry point file, add the following:\n\n    ```coffee\n    require('coffee-backtrace')\n    ```\n\n3. That's it.\n\n## Extra configuration\n\nYou can control the number of context lines shown in one of two ways:\n\n1. Start the process with the `COFFEE_BACKTRACE_CONTEXT` variable set:\n\n    ```sh\n    $ COFFEE_BACKTRACE_CONTEXT=10 coffee app.coffee\n    ```\n\n2. Use the `setContext` method on the required module:\n\n    ```coffee\n    require('coffee-backtrace').setContext(0)\n    ```\n","readmeFilename":"README.md","_id":"coffee-backtrace@0.2.1","dist":{"shasum":"fc501fdd7c34d7a97a10080e6995dd7df11f5a28","tarball":"https://registry.npmjs.org/coffee-backtrace/-/coffee-backtrace-0.2.1.tgz","integrity":"sha512-4bKVWrmMOjBgDCiJbANiNy8H7WGR6+/wR1FKv2jAVaR5N4BSvm9G5WpZ5GJyP0JB0ju7tK6wdKhoDpq+1OCqww==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDA0F29Q4RmfxJuIovCYHNMj00ODZG29lYsNROnvvkpkQIgIvThj+z5t9I11F907SmHj4hkVLlSishII09ogeEi+Tc="}]},"_from":".","_npmVersion":"1.2.12","_npmUser":{"name":"dpatti","email":"douglas.patti@gmail.com"},"maintainers":[{"name":"dpatti","email":"douglas.patti@gmail.com"}]},"0.3.0":{"name":"coffee-backtrace","author":{"name":"Doug Patti","email":"douglas.patti@gmail.com"},"description":"Expands coffee files in uncaught exceptions to add context with the compiled Javascript","version":"0.3.0","repository":{"type":"git","url":"https://github.com/FogCreek/node-coffee-backtrace.git"},"main":"./lib/coffee-backtrace","keywords":["coffee","log","error","backtrace","debug"],"dependencies":{},"license":"MIT","readme":"# coffee-backtrace\n\nA Node.js module for servers written in CoffeeScript to aide in debugging\nuncaught exceptions.\n\n**Note:** This package is somewhat redundant with CoffeeScript 1.6.2.\nCoffeeScript will now show you the *correct* line number of the exception within\nthe coffee file. However, CoffeeScript currently only performs this expansion on\nthe file executed with the command and not on any other required file. See [pull\nrequest 2968](https://github.com/jashkenas/coffee-script/pull/2968) for possible\ninformation regarding this being available on all files.\n\n## What it does\n\nWhen an exception is thrown, unfortunately the error message and corresponding\nline number can be cryptic, as they correspond to what happened in the compiled\nJavaScript file, and not the source CoffeeScript file. This aims to reduce the\npain of debugging by finding the offending line and providing some context as\nwell. See some example output from the provided example file:\n\n```\n$ coffee example.coffee\n\nTypeError: Object [object Object] has no method 'getMessage'\n at [object Object].Relay.speak [as _onTimeout] (/home/doug/dev/coffee-backtrace/example.coffee:12:40)\n         }\n\n         Relay.prototype.speak = function() {\n>          return process.stdout.write(this.getMessage() + '\\n');\n         };\n\n         Relay.prototype.getMessage = function() {\n at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)\n```\n\nOf course, if you are using a terminal, the error is color-coded red to help it\nstand out more. The `>` are added so that the message is still able to be read\nin a log file.\n\n## How to use\n\n1. Add to your package.json dependencies and run `npm install` or run `npm install coffee-backtrace`.\n\n2. In your entry point file, add the following:\n\n    ```coffee\n    require('coffee-backtrace')\n    ```\n\n3. That's it.\n\nNote that if you are also using the `coffee-script` package in your application,\nbe sure to `require()` it *before* `coffee-backtrace`, or else it will override\nthe stack trace hooks.\n\n## Extra configuration\n\nYou can control the number of context lines shown in one of two ways:\n\n1. Start the process with the `COFFEE_BACKTRACE_CONTEXT` variable set:\n\n    ```sh\n    $ COFFEE_BACKTRACE_CONTEXT=10 coffee app.coffee\n    ```\n\n2. Use the `setContext` method on the required module:\n\n    ```coffee\n    require('coffee-backtrace').setContext(0)\n    ```\n","_id":"coffee-backtrace@0.3.0","dist":{"shasum":"8cda3533170e5fd8accc5b7cf62a03f348f513b0","tarball":"https://registry.npmjs.org/coffee-backtrace/-/coffee-backtrace-0.3.0.tgz","integrity":"sha512-wNZN2s+p7v/UyERyLihPqMRo6Ltv60ulvw6sdK+Z3bDwQYskJdB39GCF2hpZbxiHV4GwmbMZv9MiZUH2oMQj/A==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEMCIDvXhI/bDdpzVImLv05jroU/+sJVZkdY7aa2FzEilf99Ah91KKEZaNCF2KP1BwcGMX8UPB2ZHAawXHEb3+OZAgfo"}]},"_npmVersion":"1.1.59","_npmUser":{"name":"dpatti","email":"douglas.patti@gmail.com"},"maintainers":[{"name":"dpatti","email":"douglas.patti@gmail.com"}]},"0.3.1":{"name":"coffee-backtrace","author":{"name":"Doug Patti","email":"douglas.patti@gmail.com"},"description":"Expands coffee files in uncaught exceptions to add context with the compiled Javascript","version":"0.3.1","repository":{"type":"git","url":"https://github.com/FogCreek/node-coffee-backtrace.git"},"main":"./lib/coffee-backtrace","keywords":["coffee","log","error","backtrace","debug"],"dependencies":{},"license":"MIT","readme":"# coffee-backtrace\n\nA Node.js module for servers written in CoffeeScript to aide in debugging\nuncaught exceptions.\n\n**Note:** This package is somewhat redundant with CoffeeScript 1.6.2.\nCoffeeScript will now show you the *correct* line number of the exception within\nthe coffee file. However, CoffeeScript currently only performs this expansion on\nthe file executed with the command and not on any other required file. See [pull\nrequest 2968](https://github.com/jashkenas/coffee-script/pull/2968) for possible\ninformation regarding this being available on all files.\n\n## What it does\n\nWhen an exception is thrown, unfortunately the error message and corresponding\nline number can be cryptic, as they correspond to what happened in the compiled\nJavaScript file, and not the source CoffeeScript file. This aims to reduce the\npain of debugging by finding the offending line and providing some context as\nwell. See some example output from the provided example file:\n\n```\n$ coffee example.coffee\n\nTypeError: Object [object Object] has no method 'getMessage'\n at [object Object].Relay.speak [as _onTimeout] (/home/doug/dev/coffee-backtrace/example.coffee:12:40)\n         }\n\n         Relay.prototype.speak = function() {\n>          return process.stdout.write(this.getMessage() + '\\n');\n         };\n\n         Relay.prototype.getMessage = function() {\n at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)\n```\n\nOf course, if you are using a terminal, the error is color-coded red to help it\nstand out more. The `>` are added so that the message is still able to be read\nin a log file.\n\n## How to use\n\n1. Add to your package.json dependencies and run `npm install` or run `npm install coffee-backtrace`.\n\n2. In your entry point file, add the following:\n\n    ```coffee\n    require('coffee-backtrace')\n    ```\n\n3. That's it.\n\nNote that if you are also using the `coffee-script` package in your application,\nbe sure to `require()` it *before* `coffee-backtrace`, or else it will override\nthe stack trace hooks.\n\n## Extra configuration\n\nYou can control the number of context lines shown in one of two ways:\n\n1. Start the process with the `COFFEE_BACKTRACE_CONTEXT` variable set:\n\n    ```sh\n    $ COFFEE_BACKTRACE_CONTEXT=10 coffee app.coffee\n    ```\n\n2. Use the `setContext` method on the required module:\n\n    ```coffee\n    require('coffee-backtrace').setContext(0)\n    ```\n","_id":"coffee-backtrace@0.3.1","dist":{"shasum":"4decc6cd16437bd425f686df76cacc676c20a843","tarball":"https://registry.npmjs.org/coffee-backtrace/-/coffee-backtrace-0.3.1.tgz","integrity":"sha512-lYhe1YT+E3hgQzeVQhc75UnvP5mHDNVZMq2nDA+GKGPAMDN0s8sSaU7LGPnolIBmydy0TcKjCysf4uV1GLnhgw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIGKHBj7esBsq7f5fmUozw5aKtfBfGLeBxAYtmHTYBvwxAiAvnxWW6CKPj4Eozq7ker/qTNDt+gU5l6TKEiAZy/CblQ=="}]},"_npmVersion":"1.1.59","_npmUser":{"name":"dpatti","email":"douglas.patti@gmail.com"},"maintainers":[{"name":"dpatti","email":"douglas.patti@gmail.com"}]},"0.3.2":{"name":"coffee-backtrace","author":{"name":"Doug Patti","email":"douglas.patti@gmail.com"},"description":"Expands coffee files in uncaught exceptions to add context with the compiled Javascript","version":"0.3.2","repository":{"type":"git","url":"https://github.com/FogCreek/node-coffee-backtrace.git"},"main":"./lib/coffee-backtrace","keywords":["coffee","log","error","backtrace","debug"],"dependencies":{},"license":"MIT","readme":"# coffee-backtrace\n\nA Node.js module for servers written in CoffeeScript to aide in debugging\nuncaught exceptions.\n\n**Note:** This package is somewhat redundant with CoffeeScript 1.6.2.\nCoffeeScript will now show you the *correct* line number of the exception within\nthe coffee file. However, CoffeeScript currently only performs this expansion on\nthe file executed with the command and not on any other required file. See [pull\nrequest 2968](https://github.com/jashkenas/coffee-script/pull/2968) for possible\ninformation regarding this being available on all files.\n\n## What it does\n\nWhen an exception is thrown, unfortunately the error message and corresponding\nline number can be cryptic, as they correspond to what happened in the compiled\nJavaScript file, and not the source CoffeeScript file. This aims to reduce the\npain of debugging by finding the offending line and providing some context as\nwell. See some example output from the provided example file:\n\n```\n$ coffee example.coffee\n\nTypeError: Object [object Object] has no method 'getMessage'\n at [object Object].Relay.speak [as _onTimeout] (/home/doug/dev/coffee-backtrace/example.coffee:12:40)\n         }\n\n         Relay.prototype.speak = function() {\n>          return process.stdout.write(this.getMessage() + '\\n');\n         };\n\n         Relay.prototype.getMessage = function() {\n at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)\n```\n\nOf course, if you are using a terminal, the error is color-coded red to help it\nstand out more. The `>` are added so that the message is still able to be read\nin a log file.\n\n## How to use\n\n1. Add to your package.json dependencies and run `npm install` or run `npm install coffee-backtrace`.\n\n2. In your entry point file, add the following:\n\n    ```coffee\n    require('coffee-backtrace')\n    ```\n\n3. That's it.\n\nNote that if you are also using the `coffee-script` package in your application,\nbe sure to `require()` it *before* `coffee-backtrace`, or else it will override\nthe stack trace hooks.\n\n## Extra configuration\n\nYou can control the number of context lines shown in one of two ways:\n\n1. Start the process with the `COFFEE_BACKTRACE_CONTEXT` variable set:\n\n    ```sh\n    $ COFFEE_BACKTRACE_CONTEXT=10 coffee app.coffee\n    ```\n\n2. Use the `setContext` method on the required module:\n\n    ```coffee\n    require('coffee-backtrace').setContext(0)\n    ```\n","_id":"coffee-backtrace@0.3.2","dist":{"shasum":"f652f519d4d5bbf502746d15a84721bc595e8ae1","tarball":"https://registry.npmjs.org/coffee-backtrace/-/coffee-backtrace-0.3.2.tgz","integrity":"sha512-sMf0aOXE+g+s8uMnlmF5zMrGSCbXo13TArITa0+o9LnUNUOaTLQLehpP6e1R69utL9cBDU+IiRX1I11mDGTmSA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDMiRKZ35MHz5ES35nLAcEEaolv69cQRUFFx+OV69BwHQIhAKNEkH1MpLmOOMirPA+rLzG2THbo4t9RBovt9f6FJFwS"}]},"_npmVersion":"1.1.59","_npmUser":{"name":"dpatti","email":"douglas.patti@gmail.com"},"maintainers":[{"name":"dpatti","email":"douglas.patti@gmail.com"}]},"0.3.3":{"name":"coffee-backtrace","author":{"name":"Doug Patti","email":"douglas.patti@gmail.com"},"description":"Expands coffee files in uncaught exceptions to add context with the compiled Javascript","version":"0.3.3","repository":{"type":"git","url":"https://github.com/FogCreek/node-coffee-backtrace.git"},"main":"./lib/coffee-backtrace","keywords":["coffee","log","error","backtrace","debug"],"dependencies":{},"license":"MIT","readme":"# coffee-backtrace\n\nA Node.js module for servers written in CoffeeScript to aide in debugging\nuncaught exceptions.\n\n**Note:** This package is somewhat redundant with CoffeeScript 1.6.2.\nCoffeeScript will now show you the *correct* line number of the exception within\nthe coffee file. However, CoffeeScript currently only performs this expansion on\nthe file executed with the command and not on any other required file. See [pull\nrequest 2968](https://github.com/jashkenas/coffee-script/pull/2968) for possible\ninformation regarding this being available on all files.\n\n## What it does\n\nWhen an exception is thrown, unfortunately the error message and corresponding\nline number can be cryptic, as they correspond to what happened in the compiled\nJavaScript file, and not the source CoffeeScript file. This aims to reduce the\npain of debugging by finding the offending line and providing some context as\nwell. See some example output from the provided example file:\n\n```\n$ coffee example.coffee\n\nTypeError: Object [object Object] has no method 'getMessage'\n at [object Object].Relay.speak [as _onTimeout] (/home/doug/dev/coffee-backtrace/example.coffee:12:40)\n         }\n\n         Relay.prototype.speak = function() {\n>          return process.stdout.write(this.getMessage() + '\\n');\n         };\n\n         Relay.prototype.getMessage = function() {\n at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)\n```\n\nOf course, if you are using a terminal, the error is color-coded red to help it\nstand out more. The `>` are added so that the message is still able to be read\nin a log file.\n\n## How to use\n\n1. Add to your package.json dependencies and run `npm install` or run `npm install coffee-backtrace`.\n\n2. In your entry point file, add the following:\n\n    ```coffee\n    require('coffee-backtrace')\n    ```\n\n3. That's it.\n\nNote that if you are also using the `coffee-script` package in your application,\nbe sure to `require()` it *before* `coffee-backtrace`, or else it will override\nthe stack trace hooks.\n\n## Extra configuration\n\nYou can control the number of context lines shown in one of two ways:\n\n1. Start the process with the `COFFEE_BACKTRACE_CONTEXT` variable set:\n\n    ```sh\n    $ COFFEE_BACKTRACE_CONTEXT=10 coffee app.coffee\n    ```\n\n2. Use the `setContext` method on the required module:\n\n    ```coffee\n    require('coffee-backtrace').setContext(0)\n    ```\n","_id":"coffee-backtrace@0.3.3","dist":{"shasum":"98b6adf29cc94486cba9f06d63fed4b97332a6ba","tarball":"https://registry.npmjs.org/coffee-backtrace/-/coffee-backtrace-0.3.3.tgz","integrity":"sha512-isupx/aKjwG9G4ISpKoXX6DwmiimCx2IICNWK6kR54cbGV+T0D2j9YgfAsirvvy/YKsV+XZcJJGHUIqr0vXkbQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIDjBdhBblw/XaXRQDNeaHp7n8sjQ4bJHMbfOu3gSpxZ2AiB1ezQSlnnOZoUmtNJ3dMD8NqcnU65Lh+hY3pSAeSaaqw=="}]},"_npmVersion":"1.1.59","_npmUser":{"name":"dpatti","email":"douglas.patti@gmail.com"},"maintainers":[{"name":"dpatti","email":"douglas.patti@gmail.com"}]},"0.3.4":{"name":"coffee-backtrace","author":{"name":"Doug Patti","email":"douglas.patti@gmail.com"},"description":"Expands coffee files in uncaught exceptions to add context with the compiled Javascript","version":"0.3.4","repository":{"type":"git","url":"https://github.com/FogCreek/node-coffee-backtrace.git"},"main":"./lib/coffee-backtrace","keywords":["coffee","log","error","backtrace","debug"],"dependencies":{},"license":"MIT","readme":"# coffee-backtrace\n\nA Node.js module for servers written in CoffeeScript to aide in debugging\nuncaught exceptions.\n\n**Note:** This package is somewhat redundant with CoffeeScript 1.6.2.\nCoffeeScript will now show you the *correct* line number of the exception within\nthe coffee file. However, CoffeeScript currently only performs this expansion on\nthe file executed with the command and not on any other required file. See [pull\nrequest 2968](https://github.com/jashkenas/coffee-script/pull/2968) for possible\ninformation regarding this being available on all files.\n\n## What it does\n\nWhen an exception is thrown, unfortunately the error message and corresponding\nline number can be cryptic, as they correspond to what happened in the compiled\nJavaScript file, and not the source CoffeeScript file. This aims to reduce the\npain of debugging by finding the offending line and providing some context as\nwell. See some example output from the provided example file:\n\n```\n$ coffee example.coffee\n\nTypeError: Object [object Object] has no method 'getMessage'\n at [object Object].Relay.speak [as _onTimeout] (/home/doug/dev/coffee-backtrace/example.coffee:12:40)\n         }\n\n         Relay.prototype.speak = function() {\n>          return process.stdout.write(this.getMessage() + '\\n');\n         };\n\n         Relay.prototype.getMessage = function() {\n at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)\n```\n\nOf course, if you are using a terminal, the error is color-coded red to help it\nstand out more. The `>` are added so that the message is still able to be read\nin a log file.\n\n## How to use\n\n1. Add to your package.json dependencies and run `npm install` or run `npm install coffee-backtrace`.\n\n2. In your entry point file, add the following:\n\n    ```coffee\n    require('coffee-backtrace')\n    ```\n\n3. That's it.\n\nNote that if you are also using the `coffee-script` package in your application,\nbe sure to `require()` it *before* `coffee-backtrace`, or else it will override\nthe stack trace hooks.\n\n## Extra configuration\n\nYou can control the number of context lines shown in one of two ways:\n\n1. Start the process with the `COFFEE_BACKTRACE_CONTEXT` variable set:\n\n    ```sh\n    $ COFFEE_BACKTRACE_CONTEXT=10 coffee app.coffee\n    ```\n\n2. Use the `setContext` method on the required module:\n\n    ```coffee\n    require('coffee-backtrace').setContext(0)\n    ```\n","_id":"coffee-backtrace@0.3.4","dist":{"shasum":"a0316c82db6acab21b586e51c33741b70cf28845","tarball":"https://registry.npmjs.org/coffee-backtrace/-/coffee-backtrace-0.3.4.tgz","integrity":"sha512-Q+CCCMucWXpOJB+iFr99oksDaqUfcG0lYLdTbrmfAKOadCjs6oWqsNHa6JQmdnYjJ1/4pDLGO2Ml4h80vut+Sg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCID84zcprMd6YzbuEZKN/8TurYEwfPG8PolwpSptOdSuoAiBe9SnmIRwfznwXocHJ5lQgdD5Z7eAVl52dcWwhP877UA=="}]},"_npmVersion":"1.1.59","_npmUser":{"name":"dpatti","email":"douglas.patti@gmail.com"},"maintainers":[{"name":"dpatti","email":"douglas.patti@gmail.com"}]},"0.3.5":{"name":"coffee-backtrace","author":{"name":"Doug Patti","email":"douglas.patti@gmail.com"},"description":"Expands coffee files in uncaught exceptions to add context with the compiled Javascript","version":"0.3.5","repository":{"type":"git","url":"https://github.com/FogCreek/node-coffee-backtrace.git"},"main":"./lib/coffee-backtrace","keywords":["coffee","log","error","backtrace","debug"],"dependencies":{},"license":"MIT","readme":"# coffee-backtrace\n\nA Node.js module for servers written in CoffeeScript to aide in debugging\nuncaught exceptions.\n\n**Note:** This package is somewhat redundant with CoffeeScript 1.6.2.\nCoffeeScript will now show you the *correct* line number of the exception within\nthe coffee file. However, CoffeeScript currently only performs this expansion on\nthe file executed with the command and not on any other required file. See [pull\nrequest 2968](https://github.com/jashkenas/coffee-script/pull/2968) for possible\ninformation regarding this being available on all files.\n\n## What it does\n\nWhen an exception is thrown, unfortunately the error message and corresponding\nline number can be cryptic, as they correspond to what happened in the compiled\nJavaScript file, and not the source CoffeeScript file. This aims to reduce the\npain of debugging by finding the offending line and providing some context as\nwell. See some example output from the provided example file:\n\n```\n$ coffee example.coffee\n\nTypeError: Object [object Object] has no method 'getMessage'\n at [object Object].Relay.speak [as _onTimeout] (/home/doug/dev/coffee-backtrace/example.coffee:12:40)\n         }\n\n         Relay.prototype.speak = function() {\n>          return process.stdout.write(this.getMessage() + '\\n');\n         };\n\n         Relay.prototype.getMessage = function() {\n at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)\n```\n\nOf course, if you are using a terminal, the error is color-coded red to help it\nstand out more. The `>` are added so that the message is still able to be read\nin a log file.\n\n## How to use\n\n1. Add to your package.json dependencies and run `npm install` or run `npm install coffee-backtrace`.\n\n2. In your entry point file, add the following:\n\n    ```coffee\n    require('coffee-backtrace')\n    ```\n\n3. That's it.\n\nNote that if you are also using the `coffee-script` package in your application,\nbe sure to `require()` it *before* `coffee-backtrace`, or else it will override\nthe stack trace hooks.\n\n## Extra configuration\n\nYou can control the number of context lines shown in one of two ways:\n\n1. Start the process with the `COFFEE_BACKTRACE_CONTEXT` variable set:\n\n    ```sh\n    $ COFFEE_BACKTRACE_CONTEXT=10 coffee app.coffee\n    ```\n\n2. Use the `setContext` method on the required module:\n\n    ```coffee\n    require('coffee-backtrace').setContext(0)\n    ```\n","_id":"coffee-backtrace@0.3.5","dist":{"shasum":"70bc1987a20bc9a13cf081f1c83683b5259f59e9","tarball":"https://registry.npmjs.org/coffee-backtrace/-/coffee-backtrace-0.3.5.tgz","integrity":"sha512-580SNj3Qfrjd5LOaHJFldlkomMtPiWgLhrGnq1OXPgnfWdWrNJLaCniN09EwtARIou62hpUy6MVoFyyneh8gUA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQC6+aP6Npc190c78WHrIl53U4oKlnpDEN4WpJeEbA8LygIhAJxUYwb/Bu6NmT6y5+Vd29z/UVlXgPV59K+j0WyvJpO6"}]},"_npmVersion":"1.1.59","_npmUser":{"name":"dpatti","email":"douglas.patti@gmail.com"},"maintainers":[{"name":"dpatti","email":"douglas.patti@gmail.com"}]}},"readme":"# coffee-backtrace\n\nA Node.js module for servers written in CoffeeScript to aide in debugging\nuncaught exceptions.\n\n## What it does\n\nWhen an exception is thrown, unfortunately the error message and corresponding\nline number can be cryptic, as they correspond to what happened in the compiled\nJavaScript file, and not the source CoffeeScript file. This aims to reduce the\npain of debugging by finding the offending line and providing some context as\nwell. See some example output from the provided example file:\n\n```diff\n$ coffee example\nTypeError: Object #<Object> has no method 'getMessage'\n    at Object.Relay.speak [as _onTimeout] (/home/doug/dev/node-coffee-backtrace/example.coffee:13:40)\n>     }\n>\n>     Relay.prototype.speak = function() {\n>>      return process.stdout.write(this.getMessage() + '\\n');\n>     };\n>\n>     Relay.prototype.getMessage = function() {\n    at Timer.list.ontimeout (timers.js:101:19)\n```\n\nOf course, if you are using a terminal, the error is color-coded red to help it\nstand out more. The `>` are added so that the message is still able to be read\nin a log file.\n\n## How to use\n\n1. Add to your package.json dependencies or type `npm install coffee-backtrace`.\n\n2.  In your entry point file, add the following:\n\n    ```coffee\n    require('coffee-backtrace')\n    ```\n\n3. That's it.\n\n## Extra configuration\n\nYou can control the number of context lines shown in one of two ways:\n\n1. Start the process with the `COFFEE_BACKTRACE_CONTEXT` variable set:\n\n    ```sh\n    $ COFFEE_BACKTRACE_CONTEXT=10 coffee app.coffee\n    ```\n\n2. Use the `setContext` method on the required module:\n\n    ```coffee\n    require('coffee-backtrace').setContext(0)\n    ```\n","maintainers":[{"name":"dpatti","email":"douglas.patti@gmail.com"}],"time":{"modified":"2022-06-13T06:27:29.380Z","created":"2013-02-26T03:38:53.936Z","0.1.0":"2013-02-26T03:38:54.992Z","0.1.1":"2013-02-28T22:13:20.739Z","0.1.2":"2013-04-05T16:22:35.893Z","0.2.0":"2013-05-21T05:49:06.260Z","0.2.1":"2013-05-29T19:41:37.008Z","0.3.0":"2013-06-21T19:55:34.464Z","0.3.1":"2013-06-24T15:39:33.891Z","0.3.2":"2013-06-24T15:43:56.863Z","0.3.3":"2013-06-24T17:30:33.942Z","0.3.4":"2013-06-24T17:53:13.686Z","0.3.5":"2013-07-01T19:29:22.514Z"},"author":{"name":"Doug Patti","email":"douglas.patti@gmail.com"},"repository":{"type":"git","url":"https://github.com/FogCreek/node-coffee-backtrace.git"}}