-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Application errors are not logging, only generating Boom "Internal Server Error" logs #4475
Comments
I'm adding some follow up to this since its been a few weeks without any response. I've been through the documentation on logging: Here's a sample route for some Stripe webhooks I'm working on:
All I get in the terminal is
I'm probably missing something, but I've been through the docs and I think I have this configured correctly. However, the callstack for the errors are being hidden. |
You are probably not seeing the stack trace since you are using a not yet supported node runtime (v21.x), where they can go missing due to a change described in hapijs/boom#302. For the current version of hapi I would advise you to stay on node v18 for the time being. |
Runtime
node
Runtime version
21.1
Module version
huh?
Used with
hapi 21.3.2
Any other relevant information
No response
How can we help?
Ran into an issue where errors generated by application code are having their errors suppressed run in debug mode locally.
I have a route that is generating an error. When running locally, I'm just getting Boom internal server errors and not getting the actual error log messages.
I have the route wrapped in a try/catch and I can
console.error
the full logs in the catch, but I feel like there should be a global routes setting somewhere likedebug
that will just dump all errors like this to the console without needing special handling each time.Note that
failAction
below does not get triggered either.I've read up on
debug
https://hapi.dev/api/?v=21.3.2#-serveroptionsdebug though maybe I'm missing something?My current server config:
The text was updated successfully, but these errors were encountered: