fix: log error cause chain in logerror function #6837
+10
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #6462
Problem
The
logerror
function in Express was only loggingerr.stack
, which doesn't display the errorcause
property introduced in Node.js 16.9.0. This meant that error chains were not visible in logs, making debugging more difficult.Solution
Modified the
logerror()
function to explicitly log the complete error cause chain. When an error has acause
, it now logs each error in the chain with a "Caused by:" prefix for clarity.Changes
lib/application.js
-logerror()
function now iterates through the error cause chaincause
work exactly as beforeBefore
After
Testing