npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

coffee-backtrace

v0.3.5

Published

Expands coffee files in uncaught exceptions to add context with the compiled Javascript

Downloads

2

Readme

coffee-backtrace

A Node.js module for servers written in CoffeeScript to aide in debugging uncaught exceptions.

What it does

When an exception is thrown, unfortunately the error message and corresponding line number can be cryptic, as they correspond to what happened in the compiled JavaScript file, and not the source CoffeeScript file. This aims to reduce the pain of debugging by finding the offending line and providing some context as well. See some example output from the provided example file:

$ coffee example
TypeError: Object #<Object> has no method 'getMessage'
    at Object.Relay.speak [as _onTimeout] (/home/doug/dev/node-coffee-backtrace/example.coffee:13:40)
>     }
>
>     Relay.prototype.speak = function() {
>>      return process.stdout.write(this.getMessage() + '\n');
>     };
>
>     Relay.prototype.getMessage = function() {
    at Timer.list.ontimeout (timers.js:101:19)

Of course, if you are using a terminal, the error is color-coded red to help it stand out more. The > are added so that the message is still able to be read in a log file.

How to use

  1. Add to your package.json dependencies or type npm install coffee-backtrace.

  2. In your entry point file, add the following:

    require('coffee-backtrace')
  3. That's it.

Extra configuration

You can control the number of context lines shown in one of two ways:

  1. Start the process with the COFFEE_BACKTRACE_CONTEXT variable set:

    $ COFFEE_BACKTRACE_CONTEXT=10 coffee app.coffee
  2. Use the setContext method on the required module:

    require('coffee-backtrace').setContext(0)