Packages that currently do not work with io.js [List]

Let's keep track of the packages which are known to currently fail to build and the corresponding issues opened to get these fixed. Inspired by Homebrew/legacy-homebrew#29988 and npm/npm#4430

Don't comment in this thread with the link to the issue

Do it the other way around: Paste a link to this issue as a comment in the corresponding issue in the failing project's issue. This way, we'll get a nice list of open/closed/merged icons in here.

edit: removed checklist, too many packages now to keep list up to date

the bunyan failure (and many more beyond this) will be coming from dtrace-provider, I've had success with a PR for NAN over there in the past, someone should probably do that for just a NAN version bump

@rvagg

@rvagg if only they'd used the caret in their semver

edit: PR submitted

mmmagic updated to nan 1.5.1 and was verified to work, so that box can be checked. :-)

node-sass has landed a change that should bring io.js support in the next release.

bcrypt's patch landed and released as 0.8.1

zmq should be fixed as well

I hope that the msgpack guys will take a look at my PR soon.

Sequelize fails sequelize/sequelize#2966

anyone want to venture on how to get the kerberos module working nodejs/nan#257

@ralphtheninja

@ralphtheninja See the initial comment, there's a remark, in bold:
"Don't comment in this thread with the link to the issue" etc.

@mzgol

@mzgol I'm an idiot. Cleaning up :)

Seems to be an issue with fs-xattr:

npm ERR! fs-xattr@0.1.5 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the fs-xattr@0.1.5 install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the fs-xattr package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild

Env: iojs v1.0.3, npm v2.2.0.

update nan for iojs compatibility

verified that zmq is not working yet, still fails on NaN

also node-inspector does not compile yet.

Added support for io.js v1.0 release.

@timoxley

@timoxley Yeah it is. My general idea behind it was not to install a release globally but rather download and unpack binaries and run e.g. /usr/local/lib/iojs-:version-linux-x64/bin/npm i :pkg for different values of :version/:pkg and check the exit code to see if the install succeeded or not. Obviously you could make this more generic for different architectures.

Naturally you could have false positives where the installation didn't work because of a broken package and not because of something that changed in npm. But for packages that you know should be possible to install it could be useful.

Can someone explain why so many modules don't work with io.js? What is the root cause?

@ralphtheninja

@ralphtheninja my assumption was that all those issues you created for packages that were broken were done from some kind of script :)

@matthewp the v8 that is in node 0.10 is over two years old and the one in io.js is quite recent. v8 has changed their API in that two year gap and the modules that have broken are all "native" modules that us v8's C++ API. The solution for most if not all of these has been to transition them to nan which is a module that people can use instead of v8 directly and deals with the v8 changes supporting several releases.

@mikeal

@mikeal ... do you have any sizing yet on just how many modules in npm may be impacted in this way by the v8 upgrade?

@jasnell

@jasnell whatever packages you see here and their dependants.

This would be the same issue with a node 0.12.

@mikeal

@mikeal Hehe nope. It was hard manual labor ;)

@ralphtheninja

@ralphtheninja dayum, I'll try to automate this then :)

I have created a little script that gets all npm projects linked to this issue and checks if any of your dependencies contain one of these projects

see here
https://github.com/mderazon/iojs-dep-check

@mderazon

@mderazon nice work! I don't see why you shouldn't just publish that to NPM, i'm sure there are plenty of packages that might break / become irrelevant / hasn't been tested 😉

@mansona

@mansona valid point, published to npm
https://www.npmjs.com/package/iojs-dep-check

@yosuke-furukawa

@yosuke-furukawa sequelize works with io.js now

gc-profiler - or would it work with latest NAN?

Works now: bretcope/node-gc-profiler#3

New thread for io.js 2.x.x: #1620

Navigation Menu

Repository navigation

Packages that currently do not work with io.js [List] #456

Don't comment in this thread with the link to the issue

7 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Packages that currently do not work with io.js [List] #456

Description

Don't comment in this thread with the link to the issue

Activity

rvagg commented on Jan 16, 2015

timoxley commented on Jan 16, 2015

mscdex commented on Jan 16, 2015

appsforartists commented on Jan 17, 2015

Fishrock123 commented on Jan 19, 2015

ckaatz-here commented on Jan 19, 2015

sdepold commented on Jan 19, 2015

yosuke-furukawa commented on Jan 20, 2015

christkv commented on Jan 20, 2015

mgol commented on Jan 20, 2015

ralphtheninja commented on Jan 20, 2015

DomT4 commented on Jan 21, 2015

ckaatz-here commented on Jan 21, 2015

7 remaining items

ralphtheninja commented on Feb 3, 2015

matthewp commented on Feb 5, 2015

mikeal commented on Feb 5, 2015

jasnell commented on Feb 5, 2015

Fishrock123 commented on Feb 5, 2015

ralphtheninja commented on Feb 5, 2015

mikeal commented on Feb 5, 2015

mderazon commented on Feb 8, 2015

mansona commented on Feb 8, 2015

mderazon commented on Feb 9, 2015

sdepold commented on Feb 11, 2015

megastef commented on Feb 17, 2015

Fishrock123 commented on May 13, 2015

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions