Stack trace
Paste minified production stack trace
Source map
Upload a .map file. It is parsed locally in your browser and never uploaded.
Resolved output
Readable stack trace and diagnostics
Resolved stack trace will appear here
Paste a stack trace, upload a source map, then resolve the frames.
Semua proses terjadi lokal di browser. Stack trace dan source map tidak pernah diunggah.
What is Source Map Stack Trace Resolver?
Source Map Stack Trace Resolver maps minified JavaScript stack frames back to original source files, line numbers, columns, and symbol names using a Source Map v3 file. It is built for frontend, React Native, Node.js, and fullstack engineers who need to debug production logs from bundled code without sending stack traces or maps to a server.
How to use
1. Paste a production stack trace from Chrome, Firefox, Safari, Node.js, React Native, Sentry, Datadog, or a browser log. 2. Upload the matching .map file generated by Webpack, Vite, Rollup, Metro, esbuild, or another bundler. 3. Click Resolve Stack Trace to inspect the readable output, frame table, and diagnostics. 4. Copy or download the resolved stack trace for an issue, incident note, or debugging session.
Features
- Parses Chrome/V8, Firefox/Safari, Node.js, React Native main.jsbundle, and generic file:line:column frames. - Resolves frames with @jridgewell/trace-mapping in the browser. - Highlights unresolved frames caused by missing columns, mismatched maps, or missing mappings. - Shows source map metadata, diagnostics totals, copy, download, and a sample stack trace loader. - Persists only the pasted stack trace after navigation; uploaded source maps remain in browser memory.
Limitations
The MVP resolves one source map at a time, so traces spanning multiple generated bundles may show unresolved frames until multi-map support is added. Frames without columns cannot be mapped accurately because source maps require generated line and column positions. Very large maps are capped at 25 MB to keep the browser responsive.