gaearon/stack-frame — explained in plain English
Analysis updated 2026-07-17 · repo last pushed 2017-05-09
Build an error reporting tool that shows clean, readable stack traces
Create a debugging dashboard that lists function name, file, and line for each error frame
Display user-facing error messages instead of raw cryptic stack text
Add stack trace parsing to an error tracking service
| gaearon/stack-frame | 00kaku/wp-rest-playground | chalarangelo/mini-active-record | |
|---|---|---|---|
| Stars | 5 | 5 | 5 |
| Language | JavaScript | JavaScript | JavaScript |
| Last pushed | 2017-05-09 | — | — |
| Maintenance | Dormant | — | — |
| Setup difficulty | easy | hard | easy |
| Complexity | 2/5 | 3/5 | 1/5 |
| Audience | developer | developer | vibe coder |
Figures from each repo's GitHub metadata at analysis time.
A JavaScript toolkit that parses messy browser error stack traces into clean, structured objects with function name, file, and line number.
Mainly JavaScript. The stack also includes JavaScript.
Dormant — no commits in 2+ years (last push 2017-05-09).
Setup difficulty is rated easy, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.