Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better OOTB error handling #4535

Open
damusix opened this issue Nov 16, 2024 · 0 comments
Open

Better OOTB error handling #4535

damusix opened this issue Nov 16, 2024 · 0 comments
Labels
feature New functionality or improvement

Comments

@damusix
Copy link
Contributor

damusix commented Nov 16, 2024

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.

@damusix damusix added the feature New functionality or improvement label Nov 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New functionality or improvement
Projects
None yet
Development

No branches or pull requests

1 participant