-
Notifications
You must be signed in to change notification settings - Fork 58
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
Support nodejs 12 #55
Comments
Hi @Apollon77 . I'll have a look in the next days. Shouldn't be hard to fix. I'm currently rewriting this module for NAPI in my rare spare-time, so in the future major version changes will be less error-prone. |
Thank you very much. I know that these changes are a pain ... I also have one „binary package“ Modul to maintain :-( |
@mathiask88 FYI (because I got a build failure notification from AppVeyor for this project for some reason): node 12 is not supported yet, but there's a workaround: appveyor/ci#2921 (comment) |
@vweevers It is no real "workaround" |
I decided for ourt perojects to switch to the "workaround method". I'm better with "latest from a certain version chain" then some old stuff, so I can tell the customers "update your node" first ... |
AppVeyor now has node v12 in their build images, but to be future-proof see 6738c97 :) |
Current build errors:
The text was updated successfully, but these errors were encountered: