Extend VError support to include Error Cause proposal support #665
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I was about to open a PR doing the same thing --- strong support from here 👍, we are currently extending the error serializer in all projects to support this. |
|
@hypesystem I would suggest switching to Pino if you can. Its pretty much equivalent + but more maintained + has eg this feature merged through pinojs/pino-std-serializers#78 |
|
I use pino for a bunch of projects, but the two aren't exactly equivalent, and there are plenty of situations where the cost of migrating is higher than the benefit 😄 |
rpaterson
approved these changes
Mar 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See https://github.com/tc39/proposal-error-cause and tc39/proposal-error-cause#31 – a stage 3 proposal for including a VError style property to the JS language itself.