-
Notifications
You must be signed in to change notification settings - Fork 52
Parsing a stack trace in Node.js throws an exception #45
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
Comments
I have a work around to this problem. Code like this doesn't work:
This code does work:
This is no longer a crucial problem for me, but would be nice if it would work because that's a common coding idiom in JavaScript. |
What also works is following:
I think the problem is that if one invokes parse without the outer scope/object, this will be undefined in https://github.com/stacktracejs/error-stack-parser/blob/master/error-stack-parser.js#L27 |
I merged #74 to address this and published v2.1.0 |
Hi thanks for this library. It looks great all though I've had some problems getting off the starting block with it.
I've prepared an example project which I believe should work but while parsing a stack trace from an exception it throws an error.
Expected Behavior
No exception should be thrown while parsing the stack trace in the example project.
Current Behavior
The following exception is thrown while parsing the stack trace in the example project:
Steps to Reproduce (for bugs)
I've prepared an example repository:
https://github.com/ashleydavis/stack-trace-test
Clone the repo. Or download and unpack the repo.
Use
npm install
to install dependencies.Use
npm start
to run the example project.The exception mentioned above is thrown.
Context
I was hoping to use your stack trace parser in my project, but I've been blocked from using it by some basic problems. This is just the first issue, if we can solve this one I'll prepare an example that demonstrates the next problem.
Your Environment
Possible Solution
Sorry, no idea.
The text was updated successfully, but these errors were encountered: