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

atma-loader-stacktrace

v0.1.1

Published

Stacktraces for compiled/minified scripts

Downloads

210

Readme

Stacktraces for compiled and minified files

Use correct linenumber and filenames in errors for better debugging.

Usage
$ npm i atma-loader-stacktrace -s
# not already included `atma-io`? Then:
$ npm i atma-io -s
require('atma-loader-stacktrace')({
	//@default false
	handleUncaughtExceptions: true
});

// after this line of code all error objects will have original filenames, linenumbers
Minified files
lib/
   foo.js
   foo.min.js
   foo.min.js.map

Now you can require('./lib/foo.min.js') and on errors you will see the normalized path to foo.js with proper line numbers. Any time the error occure this library will pick up the source maps (if exists *.map)

Compiled files

As for example, refer to atma-loader-traceur.

lib/
	foo.es6

atma-loader uses atma-io to load and dynamicaly compile the sources. And this library registers virtual files with the extension e.g. *.es6.map, so now after an error occures it will load the sourcemaps for the foo.es6 file and correctly replace the linenumber for better debuggin.


(c) MIT