iojs

[dtinth]

Just to see if io.js works in current state. To get this merged, we need to:

• make sure that some tasks (e.g. automated code reviews) are only done by a single job (not by every worker in build matrix)

Closes #64

[coveralls]

Coverage remained the same at 98.97% when pulling 9681b54 on iojs-travis into 18265a0 on master.

[coveralls]

Coverage remained the same at 98.98% when pulling bc23fa9 on iojs-travis into 6edad46 on master.

[dtinth]

Current obstacles:

• Update kexec for iojs support babel/babel#691
• io.js 1.1 support sass/node-sass#627
• Error: Module did not self-register. with Node 0.12 installed sass/node-sass#653

[coveralls]

Coverage increased (+0.01%) to 99.1% when pulling 9e9feb3 on iojs-travis into df075be on master.

[dtinth]

Abandoned. Settle with Node.js 0.12. io.js is a new player, but too new, that not every library we depend on fully support it. For example, node-sass.

At first, I thought of dropping node-sass and use LESS. But thinking about it again, both node-sass and Node is more mature than io.js.

io.js releases new version so often—too often. The version number went from 1.2.0 to 1.5.0 in less than a month, while node-sass is still only supporting io.js 1.2 as of time of writing and couldn't handle binary module install correctly.

Until all of our our (more mature) dependencies work with io.js' rapid release cycle, I think it's safer to stick with Node v0.12. Otherwise, our build may break every time a new io.js v1.x is released and we have to wait until they fix it.