Standard JavaScript error stack traces only show the current call stack, leaving developers to hunt for root causes using breakpoints or console.logs. A proposed improvement would enrich error traces with preceding function calls and their arguments and return values — essentially mixing tracing with error stacks. This would let developers immediately see which function returned an unexpected value (like undefined) without manually instrumenting code. The idea is to enable this enhanced tracing mode only when DevTools is open, capturing only recent traces to minimize performance impact.
Sort: