-
-
Notifications
You must be signed in to change notification settings - Fork 817
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 for node8 #826
Comments
Ohp, I just saw #825! I'll give this another shot, and report back if I can get it to work. |
I don't know what caused this originally, but all seems to be OK :) Might be worth tweaking the readme if node8 is officially supported? |
Turns out this is happening due to a behavior change in npm5: npm/npm#16926. I recommend working around this by sticking to node v6 for now - refs mapbox/node-pre-gyp#298 (comment) |
Ah, that makes sense. Thanks for taking a peek. |
When I attempted to use node8/npm5 with my application, it caught a snag trying to install this package. I didn't necessarily expect it to work, given that the readme of this module makes it clear that support only goes through node7 today– this is just a feature request. Let me know if I can be useful with more information or possibly with any newcomer-friendly contributions to this module. Here's the error I got during install,
The text was updated successfully, but these errors were encountered: