-
Notifications
You must be signed in to change notification settings - Fork 68
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
won't install on node 6 #80
Comments
Can you provide the output of |
|
The failure mode is a hallmark of using an outdated version of nan. The dependency in the package incorrectly says ^2.0.8, when it really should be at least something closer to 2.3.3 (see #74 and #75). Since npm installs the newest acceptable version, the only way I know this could become a problem at build-time is if dtrace-provider is used inside another project that explicitly uses an old version of nan. But I don't see that in your "npm ls" output. Can you tell which version of nan was pulled in when npm tried to install dtrace-provider? |
I typed "npm install dtrace-provider" at the command line ... There is a version of 'nan' in the node_modules folder marked as "version": "2.0.9", but what causes this to appears here is beyond my abilities to determine, without a complete trawl of the node_mofdule folder and all sub folders looking for references. As there are 100's of folders under mode_modules this would be very long winded ... fs-events seems to include 'nan' and has this but it also include the folder nan inside it's node_modules folder, so it can use it... If your dtrace-provider has a dependency on a version higher then 2.0.8 then should it not include that dependency correctly in the package.json file so that npm can also correctly sub/nest the required version of nan under the code so that it builds ??? |
So I updated kerberos from 0.0.17 to 0.0.21 which pulled the version of nan up to V2.3.5 in the main node_modules folder. This then allows you to install dtrace-provider and it no longer errors. |
Thanks. I'm glad this is resolved for you.
Yes. See #75. Sorry for the trouble. |
when trying to install on Mac OS-X (El Capitan V 10.11.5)
I get the following trace / log
The text was updated successfully, but these errors were encountered: