Better OOTB error handling
- Dominant language
- JavaScript
- Stars
- 14.8k
- Forks
- 1.4k
- Avg merge
- 22d 3h
- Merged PRs (30d)
- 1
Description
### Runtime
NodeJS
### Runtime version
any
### Module version
21
### What problem are you trying to solve?
Whenever I make a new server and it throws, the error is caught and wrapped into a generic `Boom.internal()`, with no feedback on the original error or the stack trace. The only way to introspect is to pass `routes.ext.onPreResponse.method()` to server options.
This is a bit awkward, especially if I'm using the server for non-production cases, tests, or non-critical apps. It would be nice if the option to obfuscate errors was an opt-in / out configuration. I do understand that Hapi is this way in order to be secure by default, I just think it would be helpful
### Do you have a new or modified API suggestion to solve the problem?
Perhaps a `Hapi.server({ production: true | false })` would suffice? I am currently using `NODE_ENV` to set the `onPreResponse` options so I have good feedback at dev time.
Contributor guide
Assessment
This issue has not been assessed yet.