-
Notifications
You must be signed in to change notification settings - Fork 465
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
Not building on node 8.2.1 #99
Comments
The |
What I meant was, the change was merged into the node 8.x branch last week, so it should be in the v8.3.0 release. |
Thats probably my fault as I'm generally using master versus the releases but most module maintainers are going to be using the official releases. An earlier version would probably work, but its not necessarily easy for maintainers to know. We should only have 1-2 more cases where this happens as we should be locking things down within a few weeks. |
We should have a strategy to support node versions until we freeze the API. |
I think we can close this, please re-open if that is not the case. |
I think this is due to a semver-major change happening in core for the new error codes. In case such events happen again, this module should be released to NPM after the change lands in a release.
The text was updated successfully, but these errors were encountered: