-
Notifications
You must be signed in to change notification settings - Fork 284
io.js support #387
Comments
The problem is that it tries to use 64-bit integers. Will fix. |
@kkoopa is this fixed? confirmed working on io.js? |
Fixed, yes. Confirmed, no. It ought to work. On January 20, 2015 2:31:51 AM EET, Tim Oxley notifications@github.com wrote:
|
Confirmed. works. $ make test
./node_modules/.bin/mocha --expose-gc --slow 2000 --timeout 600000
child_process: customFds option is deprecated, use stdio instead.
# ...
43 passing (3s)
$ node -v
v1.0.3 |
Cool, thanks :) |
This still seems to be ongoing, now 7 months later. |
Then I don't think you understand the nature of Node and V8 upgrades. |
I'm not sure how my understanding has anything to do with me being unable to type |
Because during the past 7 months, multiple versions of io.js have been released many of which introduced breaking V8 API changes and thus needed a new version of NAN and code changes to adapt to the new API of NAN. Those have been happening. This is not one issue over the past 7 months, this is an ongoing challenge in keeping up-to-speed with io.js (and more importantly: V8) releases. Look at any NPM module with a native component and you'll see the exact same ongoing challenge in the issue tracker. @kkoopa has been doing an amazing job at keeping node-zmq up to date as fast as possible after each new io.js release. What then follows is a node-zmq release. Please have a little patience, your prayers will be answered. |
this issue was fixed a while back, but the fix for iojs3 hasn't been published at the time of this comment. |
Oh by the way, you can always install the latest master of node-zmq straight from GitHub: npm install JustinTulloss/zeromq.node |
oh cool i didn't know that can you put that in package.json or do we have to use the git link? |
You can put that in package.json as the version of your dependency. |
Updating the zeromq dependency on
nan
to 1.5.x introduces support for io.js, but seems some code changes are required to get this to successfully build on io.js 1.0.1.The text was updated successfully, but these errors were encountered: