-
Notifications
You must be signed in to change notification settings - Fork 15
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
build fails for node v10 #3
Comments
I've made a PR to fix this: #4 I had just found a similar issue in another package (noble/node-bluetooth-hci-socket#84) with a fix for the same problem, which I just copied and it works, to make it build with Node v10. Should not break anything with earlier versions, as long as they update the NaN dependency to ^2.10. CI tests have failed, but that seems to be caused by a faulty test environment config (missing GitHub token for some NPM packaging preparation script). Actually only the first three commits here (up until ae9ea9b) should be included. The other stuff was just me trying to make it npm/yarn-installable from that git repo (needing node-pre-gyp as a bundled dependency). Should not have gone into the PR. My bad. But I think one can pick commits to merge? If not, I can separate that out. |
Thanks I saw the error on appveyor, I merge your PR to be able to use with node v10 |
I merged your request but you can fix some thing like the node modules folder, the package.json, Sorry I do not have the time to work on it . I Add you to contribute |
Thanks. I'll see what I can do. Also quite busy at the moment and not really well-versed in this stuff. I had included the node_modules directory with the pre-gyp bundled dependency stuff into git because that was missing when I simply tried to package.json was updated to include nan ^2.10. Not sure how the CI stuff works. |
Hello!
I am trying to use this package in a project with Nodejs version 10, which fails.
It works with Nodejs version 9. But is there any chance to get it running with Node 10?
Here is the error output:
The text was updated successfully, but these errors were encountered: