Unexpected errors should be reported with more context
Open
- Dominant language
- TypeScript
- Stars
- 6.4k
- Forks
- 128
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 4
Description
We usually know what script we're running when an unexpected error occurs, so at minimum we couldwrap unexpected errors with the script context and include it when we display it.
There might also be additional context we could add to help narrow down where in the code the error occurred. Especially given the fact that `fs` errors in Node don't include stack traces (https://github.com/nodejs/node/issues/30944).
Contributor guide
Assessment
This issue has not been assessed yet.