doc: correct description of error.stack accessor behavior
#61090
+8
−3
Conversation
This file contains hidden or 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
Contributor
|
Should we mention https://github.com/tc39/proposal-error-stack-accessor, which I think is what triggered the change in V8? |
Member
Author
|
@ljharb reckon this is mature enough to reference on our side? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The existing description in errors.md is outdated as of v21.x:
thisvalue passed to the getter/setter is not a native error.This behaviour isn't mentioned in V8/Chromium documentation nor MDN, so it's worth spelling out here.
Error.isError()doesn't exist in v22.x, so this will need a specific PR referencingutil.types.isNativeError()instead.Refs: #60862