Repository navigation
Packages that currently do not work with io.js [List] #456
Description
Activity
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 if only they'd used the caret in their semver
edit: PR submitted
mmmagicupdated 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.
Sequelizefails sequelize/sequelize#2966anyone want to venture on how to get the kerberos module working nodejs/nan#257
@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 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 rebuildEnv: iojs v1.0.3, npm v2.2.0.
- added a commit that references this issue
on Jan 21, 2015 verified that zmq is not working yet, still fails on NaN
also node-inspector does not compile yet.
- added a commit that references this issue
on Jan 21, 2015 7 remaining items
@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 :pkgfor different values of:version/:pkgand 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 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
nanwhich is a module that people can use instead of v8 directly and deals with the v8 changes supporting several releases.@jasnell whatever packages you see here and their dependants.
This would be the same issue with a node 0.12.
@mikeal Hehe nope. It was hard manual labor ;)
@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
@mansona valid point, published to npm
https://www.npmjs.com/package/iojs-dep-check@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
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