-
Notifications
You must be signed in to change notification settings - Fork 505
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
Add node 12 support #850
Add node 12 support #850
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me - thank you 👍
hmmm. It looks like appveyor hasn't caught up to node 12 yet. https://ci.appveyor.com/project/RodVagg/nan |
Should I revert the change for appveyor till this is available? |
Being that the PR isn't actually necessary for building modules against Node.js 12, I'm inclined to simply wait for Appveyor to include support for Node 12 before merge. It'll likely happen within days... |
Any news? Thanks. |
Refs: appveyor/ci#2921 |
This is test PR, adding windows build support to Travis. It's an alternative for nodejs#850 to waiting for appveyor support. IME, Travis windows builds are a fair bit slower than appveyor, but I've also had plenty of false positives on appveyor tests, so it's a mixed bag.
For anyone that's anxious for this to be merged, I've created a first step in #853 that adds Travis' windows support. It'll need a little help though to get it working. |
Thanks, landed in e512f92. |
@bnoordhuis thanks for merge, can you publish new version on npm too? |
No real need. Except for the |
No functional change, just update readme, CI and add
NODE_12_0_MODULE_VERSION
.Refs: #849