Skip to content

Better OOTB error handling #4535

Description

@damusix

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureNew functionality or improvement

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions