mifi / stacktracify

CLI to make unreadable production stack traces readable using source maps

stacktracify

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

...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

npm install -g stacktracify

Usage

Copy a minified stacktrace to your clipboard - then run:

stacktracify /path/to/js.map

Can also read stacktrace from file. For more info:

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)

stacktracify's Issues

Support multiple file sourcemaps

It would be very useful if you could provide a folder of sourcemaps, that way you don't have to run the command for each file in chunked build scenarios.

Support invoking from code

I need something very similar, but to use in javascript/typescript itself.

Scenario: I have a serverside express API, with an endpoint that logs errors from frontend (/api/log/). I send a JSON-string of the whole error-object to this endpoint. I would like the express server to "stacktracify" the error.stack and error.componentStack, before logging it further.

If this sounds like a good idea, I could try help get that kind of functionality into this repo, instead of creating yet another repo/application that demystifies stack traces?

(I guess it would involve making a different "bin"-file for the current functionality, and esm-export a function from the index-file. Or change "main" from index.js to another file exporting the core functionality.)

Print also code line

Like source-map-cli does:

Maps to source.js:2:10 (baz)

   return baz(bar);
          ^

Provide output in the documentation

Maybe you should add an output of the stacktrace after stacktracify command in the README.md file ?

Thanks !