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

@_baba/stack-mapper

v0.0.1

Published

A CLI tool to map stack traces to source code.

Downloads

4

Readme

stack-mapper

A CLI tool to map stack traces to source code.

Usage

$ npm install -g @_baba/stack-mapper

Usage: stackmapper [options]

Options:
  -v, --version         output the version number
  -s, --stack <string>  The error stack trace
  -m, --map <string>    The source map directory
  --verbose             Verbose output (default: false)
  -h, --help            display help for command

Example

$ stack-mapper -s "TypeError: Cannot read properties of undefined (reading 'children')
    at tab.js:2:2942105
    at Array.map (<anonymous>)
    at Hk (tab.js:2:2941959)
    at ii (tab.js:2:248044)
    at Ui (tab.js:2:257436)
    at qc (tab.js:2:300769)
    at Ol (tab.js:2:287143)
    at Sl (tab.js:2:287071)
    at El (tab.js:2:286934)
    at yl (tab.js:2:283931)" -m "./"
------- STACK TRACE -------
TypeError: Cannot read properties of undefined (reading 'children')
    at children (webpack://app-tab/src/components/AppTab/index.tsx:443:32)
    at Array.map (<anonymous>:null:null)
    at map (webpack://app-tab/src/components/AppTab/index.tsx:431:34)
    at c (webpack://app-tab/node_modules/react-dom/cjs/react-dom.production.min.js:157:243)
    at Ch (webpack://app-tab/node_modules/react-dom/cjs/react-dom.production.min.js:180:153)
    at li (webpack://app-tab/node_modules/react-dom/cjs/react-dom.production.min.js:269:342)
    at ck (webpack://app-tab/node_modules/react-dom/cjs/react-dom.production.min.js:250:346)
    at bk (webpack://app-tab/node_modules/react-dom/cjs/react-dom.production.min.js:250:277)
    at ak (webpack://app-tab/node_modules/react-dom/cjs/react-dom.production.min.js:250:137)
    at Tj (webpack://app-tab/node_modules/react-dom/cjs/react-dom.production.min.js:243:162)

Testing

The fixtures are generated from the vite

export function setupCounter(element: HTMLButtonElement) {
  let counter = 0;
  console.log(new Error("test").stack);
  const setCounter = (count: number) => {
    counter = count;
    element.innerHTML = `count is ${counter}`;
  };
  element.addEventListener("click", () => setCounter(counter + 1));
  setCounter(0);
}

Why I wrote this tool

sourcemapping is the tool that I used in the past, but it is not maintained for a long time and sometime I found that it was not working for some reason.

I never write a CLI tool like this before, so I just try to write a new one ;)

Reference