DX: Cleaner stack traces

This is an idea for cleaner stack traces pointing directly to where errors exist.

https://github.com/sindresorhus/clean-stack

console.log(error.stack);
/* Before
Error: Missing unicorn
    at Object.<anonymous> (/Users/sindresorhus/dev/clean-stack/unicorn.js:2:15)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Function.Module.runMain (module.js:441:10)
    at startup (node.js:139:18)
*/

console.log(cleanStack(error.stack));
/* After
Error: Missing unicorn
    at Object.<anonymous> (/Users/sindresorhus/dev/clean-stack/unicorn.js:2:15)
*/

I’m playing around with this idea right now.

I would love to hear feedback from the community.

Any potential downsides to this?

[DavidWells]

Yeah maybe it should work like:

With SLS_DEBUG off (aka default)

• showing shorter clean stack traces for every error
• mapping common errors with human friendly messages/links to helpful docs (error tracking should help in this regard)

With SLS_DEBUG on

• showing verbose (infinite traces https://github.com/serverless/serverless/issues/3579)

[medikoo]

Closing as it was probably addressed in best possible way with https://github.com/serverless/serverless/pull/6502

Now we show stack traces only for programmer errors (so unexpected crashes that in all cases signal a bug) or when user has set SLS_DEBUG. In all other cases we show only error message which is expected to be meaningful enough (if it’s not it’s an error reporting bug)