-
Notifications
You must be signed in to change notification settings - Fork 135
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
TypeError: Error.captureStackTrace is not a function #211
Comments
Same is still true for all versions of node above v7.0.1. I've tested on 7.3.1 and 8.0.0 nightlies and getting the same results. If it is a node issue it doesn't seem to have been addressed yet. I was going to look at a PR but I don't know coffee well enough and solves to similar problems in other packages seem quite involved. |
any ideas about how to fix it? I would like to use nodejs version 7.4.0 for async await functionality with harmony. Thanks. |
I figured out a fix. see my post |
This is not a fix, but rather hack. I found that this repo isn't very maintained. Switched to officially supported https://github.com/neo4j/neo4j-javascript-driver |
it's on my TODO list, to upgrade to the new drivers. was your upgrade painful? I've been putting it off because everything's a rabbit hole |
…ith default Error class. fixes thingdom#211
…ith default Error class. fixes thingdom#211
…ith default Error class. fixes thingdom#211
Is there a any news? |
I resorted to using https://github.com/neo4j/neo4j-javascript-driver for many reasons and it is working well. |
yeah. I did the upgrade as well. it was painful as expected but definitely worth the effort |
Upgrading to supported driver is the solution, move away from this repo in the meanwhile. |
Yeah, I'm getting this error as well. Anyone know when it will be fixed? |
@willynilly never I think :) just use official repo - https://github.com/neo4j/neo4j-javascript-driver |
I get this error after upgrading the Nodejs version from
v6.9.2
tov7.0.1
It might be the V8 issue (bumped up version in Nodejs 7 to v8 5.4)
I guess we should call the global one
global.Error.captureStackTrace(this, this.constructor);
The text was updated successfully, but these errors were encountered: