Skip to content
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

Update nan version #13

Closed
wants to merge 1 commit into from
Closed

Update nan version #13

wants to merge 1 commit into from

Conversation

domosapien
Copy link

Supports nodev6

Supports nodev6
@slnode
Copy link

slnode commented Jun 14, 2016

Can one of the admins verify this patch? To accept patch and trigger a build add comment ".ok\W+to\W+test."

@domosapien domosapien mentioned this pull request Jun 14, 2016
@sam-github sam-github self-assigned this Jun 14, 2016
@@ -24,7 +24,7 @@
"tap": "^1.3.2"
},
"dependencies": {
"nan": "^2.0.5"
"nan": "^2.3.5"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This has no purpose, we don't depend on any feature added in 2.3, and npm will always install the latest matching, and ^2.0.5 matches 2.3.5, so it will get installed.

Why did you think this necessary?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not well versed in semver, and double checking the docs confirms that ^2.0.5 matches 2.3.5. However, trying to build on node v6.2.1 and npm 3.9.6, I get the errors shown in #14. Upgrading nan to 2.3.5 in the package.json fixes the issue. Is there something else I am missing?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, what you probably noticed is that npm install does not update dependencies. so if you had previously installed, had an old nan, then installed again, nan would not be updated. then, I bet you did something like npm install --save nan or something of the like, and that caused it to update nan, and also update the package.json. the latter was irrelevant, the nan update was what helped you.

Anyhow, do this: rm -rf node_modules; npm i and you will find that you get latest versions.

@sam-github
Copy link
Contributor

FYI, ci is green across all the major node versions: http:https://ci.strongloop.com/job/modern-syslog/, 5 and 6 included.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants