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 🙏

© 2026 – Pkg Stats / Ryan Hefner

coffee-source-map

v1.0.2

Published

Implementation of v3 sourcemaps in coffee-script.

Readme

This is a library for reading and writing v3 source maps. It is based on work done by Jason Walton and Jeremy Ashkenas to add source map support to coffee-script.

Usage

Fixing exception stack traces

Suppose you're working on a large project, and you pre-compile your .coffee files into .js files to speed up performance, but you want to keep your stack traces pretty:

SourceMap = require 'coffee-source-map'
SourceMap.registerErrorHandler()

Whenever an exception stack trace is rendered, this will try to open every .js file in the stack trace, find the associated .map file, and fix up the exception.

Reading source maps

You can read a SourceMap from a string with:

mapString = fs.readFileSync mapFileName, "utf-8"
sourceMap = SourceMap.load mapString, generatedFileName

If you have a generated file with a //# sourceMappingURL=... line, you can load the map from the generated file:

sourceMap = SourceMap.loadForSourceFileSync generatedFileName

Once you have a sourceMap, you can query it to get source code file names and positions:

[sourceFile, sourceLine, sourceColumn] = sourceMap.sourceLocation [generatedLine, generatedColumn]

Note that all values are 0-based!

Writing source maps

Generate a source map and add mappings to it with:

sourceMap = new SourceMap generatedFile
sourceMap.add(
    sourceFile,
    [sourceLine, sourceColumn],
    [generatedLine, generatedColumn]
)

You can write a v3 source map with:

v3Map = sourceMap.generate {sourceRoot: ""}