We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi! Transitioning from quickjs, I was to having the filename (JS_ATOM_fileName), line (JS_ATOM_lineNumber) and column (JS_ATOM_columnNumber) on the Error object. I think they were added in the build_backtrace method (https://github.com/bellard/quickjs/blob/6e2e68fd0896957f92eb6c242a2e048c1ef3cae0/quickjs.c#L6559).
JS_ATOM_fileName
JS_ATOM_lineNumber
JS_ATOM_columnNumber
Error
build_backtrace
It was useful when you want to offer to the user some indication of where the error comes from without displaying the whole stack trace.
The text was updated successfully, but these errors were encountered:
I can't seem to find it now, but IIRC we removed those because they are nonstandard.
You can use Error.prepareStackTrace to add them to the error object if you need to.
Sorry, something went wrong.
No branches or pull requests
Hi! Transitioning from quickjs, I was to having the filename (
JS_ATOM_fileName
), line (JS_ATOM_lineNumber
) and column (JS_ATOM_columnNumber
) on theError
object. I think they were added in thebuild_backtrace
method (https://github.com/bellard/quickjs/blob/6e2e68fd0896957f92eb6c242a2e048c1ef3cae0/quickjs.c#L6559).It was useful when you want to offer to the user some indication of where the error comes from without displaying the whole stack trace.
The text was updated successfully, but these errors were encountered: