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

unstacktracify

v2.0.0

Published

Make unreadable and poorly formatted production stacktraces readable using source maps

Downloads

126

Readme

unstacktracify

Have you ever been faced with a stacktrace that looks like this?

TypeError h is not a function. (In 'h()', 'h' is undefined)
    main.jsbundle:954:5353
    main.jsbundle:112:423 p
    main.jsbundle:112:1740
    main.jsbundle:112:423 p
    main.jsbundle:112:898 n
    main.jsbundle:112:1273
    main.jsbundle:50:205 c
    main.jsbundle:50:1623 b
    main.jsbundle:50:488 _
    [native code] value
    [native code] value

or worse, one that looks like this?

Error: Syntax Error
!    at ms (source.js:2:2440991)
!    at ms (source.js:2:2441064)
!    at ds (source.js:2:2440502)
!    at Oc (source.js:2:2454651)
!    at t.unstable_runWithPriority (source.js:2:783491)
!    at Go (source.js:2:2400035)
!    at wc (source.js:2:2452730)
!    at sc (source.js:2:2448884)
!    at source.js:2:2400326
!    at t.unstable_runWithPriority (source.js:2:783491)

...perhaps from production from a minified web JS bundle or a React Native error report.

stacktracify takes a source map and a stack trace from your clipboard (or from a file) and outputs a readable stacktrace with proper line numbers for each line

Example output:

TypeError h is not a function. (In 'h()', 'h' is undefined)
    at getAuthToken (logic/api.js:67:20)
    at authRequest (logic/api.js:127:8)
    at data (logic/SaveQueue.js:30:20)
    at op (logic/SaveQueue.js:43:29)
    at __callImmediates (node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:143:11)

Install

yarn add unstacktracify

Usage

Copy a minified stacktrace to your clipboard - then run:

yarn stacktracify /path/to/source-maps

Can also read stacktrace from file. For more info:

yarn stacktracify --help

See also

  • https://github.com/gabmontes/source-map-cli (only takes one line at a time)
  • https://github.com/janekp/mapstrace (not a CLI, not easy to use for any stack trace)