csnover/TraceKit

Add support for source maps?

Open

#31 opened on Aug 13, 2015

View on GitHub
 (13 comments) (0 reactions) (0 assignees)JavaScript (1,017 stars) (174 forks)batch import
enhancementfeature requesthelp wanted

Description

Cloning over from https://github.com/occ/TraceKit/issues/61:

Adding support for getting cleaner stack traces from minified JS files via source maps would be pretty amazing.

Can leverage mozilla/source-map project for decomposing sources in ES5-compliant browsers

Contributor guide

Tech stack
javascriptnodejs
Domain
developer experiencetooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScript proficiencySource map conceptsTraceKit internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
First, review the current stack trace parsing logic in TraceKit, primarily in `tracekit.js`. Next, study the `mozilla/source map` library to understand how to consume source maps. Then, examine the 13 comments on this issue for additional context and suggestions. Finally, design an integration that maps minified stack frames to original source locations using the source map library, ensuring compatibility with existing TraceKit output.