Support node v4+/io.js release candidates

[ljharb]

This issue is to track adding support for io.js release candidates. The same process will work for node post-merge.

[ljharb]

Linking to nodejs/node#2097 (comment) and #712, pinging @rvagg @Fishrock123

[rvagg]

Sweet, the 3.0's are available at https://iojs.org/download/rc/ and a really nice except for the fact that no native addon will build yet thanks to V8 dramas but we're getting there (track that progress here). The index.tab and index.json format is the same and we're now including a "headers" tarball that's just the source headers for compiling against.

[ljharb]

Beautiful, thanks. So far the only really annoying part for me is that version numbers aren't just vX.Y.Z, they now have a -rcN suffix :-) Working on it now though.

[ljharb]

I think I have the functionality done, but now I need to write the tests. I'll be out of the country for two weeks tomorrow, so my ability to work on this will be spotty, but hopefully I'll get it done shortly after my return if not before.

@rvagg, I won't want to merge this until the version format in nodejs/build#126 is resolved, ideally in a way where I only have to support one format for all io.js rc versions :-)

[SimenB]

Any news? Node v4 is currently in RC, would love to install it using nvm 😄

[ljharb]

This won't be done quickly; at least not for a few weeks.

[mgol]

For people who want to test the v4 rc via nvm; you can't install it via nvm but it's enough to download the proper *.tar.gz file from https://nodejs.org/download/rc/v4.0.0-rc.1/, unpack it and move it to $NVM_DIR/versions/node/v4.0.0-rc.1 and you can use it afterwards; works for me:

$ nvm use 4
$ nvm ls
    iojs-v3.3.0
       v0.10.40
        v0.12.7
->  v4.0.0-rc.1
         system
default -> node (-> v4.0.0-rc.1)
node -> stable (-> v4.0.0-rc.1) (default)
stable -> 4.0 (-> v4.0.0-rc.1) (default)
iojs -> iojs-v3.3 (-> iojs-v3.3.0) (default)
$ node --version
v4.0.0-rc.1

[ljharb]

Please note, that if you do this, it will be incompatible with the eventual nvm implementation - so please be prepared to manually clean it up in a few weeks :-)

[mgol]

@ljharb Sure. Removing one folder is easy. :)

[jalcine]

@ljharb commented on Sep 5, 2015, 8:31 PM EDT:

Please note, that if you do this, it will be incompatible with the eventual nvm implementation - so please be prepared to manually clean it up in a few weeks :-)

We'd have to wait a few weeks for iojs 4 to be available via nvm? 😞 Is there a PR one can subscribe to for info?

[jkrems]

@jalcine I don't think this applies to node 4, only to node release candidates. In hopefully a few hours node v4 proper will be out and then this whole thing is moot. :)

[jalcine]

Once it's available, rest assured you'll find me like the kid in the GIF on Twitter 👍

[mgol]

Node v4 is already out and you can install it via nvm. Just remove any manually downloaded RCs first (if you followed my previous advice).

[wadey]

Node v4 is already out and you can install it via nvm.

If I try to install Node v4 with nvm, I get this error:

$ nvm install v4.0.0
Installing node v1.0 and greater from source is not currently supported

Do I have something configured wrong?

[mgol]

@wadey Most likely you have outdated nvm. On my machine:

$ nvm --version
0.26.1

It's most likely easiest to just reinstall nvm: https://github.com/creationix/nvm#install-script

[ljharb]

@wadey you're using nvm from the master branch. Please only use nvm from a tagged release.

[wadey]

Ah, I was following the same steps nan uses to set up nvm:

• https://github.com/nodejs/nan/blob/f14e04a3492ede8ca2aac8f049a60c595d7bfbf2/.travis.yml#L24

I guess we should tell them to not use master as well.

[ljharb]

@wadey thanks, filed nodejs/nan#444 to correct that

[michaelgilley]

+1

[ljharb]

Unblocked by #1204.

[MylesBorins]

🎉🎉🎉