Stacktrace improvements
- Dominant language
- JavaScript
- Stars
- 1.9k
- Forks
- 359
- PR merge metrics
- No merged PRs in 30d
Description
There is a lot of nodeunit and async.js noise in the stacktraces... If we can _reliably_ improve the stacktraces, it would make debugging failing tests a little nicer.
I'm a bit worried about messing with something as fundamental as a stacktrace, but it might be worth experimenting with, and could be included as an option to the command line tool at first.
See: http://code.google.com/p/v8/wiki/JavaScriptStackTraceApi
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files or tests; start at the command-line tool and review the V8 JavaScript Stack Trace API linked in the report. Done means a reliable, experimentally validated reduction of nodeunit and async.js noise, with any initial behavior exposed as an explicit CLI option.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100