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

sourcemap-decorate-callsites

v2.0.0

Published

Decorate callsites with methods that return the sourcemapped file/line/column locations

Readme

sourcemap-decorate-callsites

Version npmBuild Status

Decorate callsites with methods that return the sourcemapped file/line/column locations.
Supports both file references and inline source maps.

Installation

$ npm install --save sourcemap-decorate-callsites

Usage

var errorCallsites = require('error-callsites')
var decorateCallsites = require('sourcemap-decorate-callsites')
var someModule = require('some-module')

someModule.doAsyncThing(function (err) {
  if (!err) {
    return console.log('yaywin')
  }

  decorateCallsites(errorCallsites(err), function (sourcemapErr, callsites) {
    printCallsites(err, callsites)
  })
})

function printCallsites(err, callsites) {
  console.log('Error: %s', err.message)
  callsites.forEach(function (callsite) {
    console.log(
      '  in %s:%s:%s',
      callsite.getFileName(),
      callsite.getLineNumber(),
      callsite.getColumnNumber()
    )
  })
}

How it works

  • Passed callsites are resolved to filenames
  • Filenames referenced are read from filesystem
  • Source files are traversed, looking for references to a source map (//# sourceMappingURL=some.js.map)
  • The source map is read from filesystem (or parsed from base64 in the case of inline source maps)
  • A source map consumer is created using the source-map module and cached in-memory
  • The following functions for each callsite are modified to return the information from the source map if available:
    • getFileName()
    • getLineNumber()
    • getColumnNumber()
  • When called, these functions will resolve the generated location to the original location based on the source map

Notes

  • To debug why a sourcemap can't be resolved or results in an error, you may pass DEBUG=sourcemap-decorate-callsites to your Node application, which will print debug info while resolving.

License

MIT-licensed. See LICENSE.