io.js support

[timdp]

Now that the first beta of io.js is out, it'd be great if nodist could also maintain that.

[robertd]

+1

[unlight]

+2

[AriaMinaei]

+1

[ForbesLindesay]

+1

[timdp]

For what it's worth: personally, I've switched to nvmw until nodist gets io.js support.

Because nvmw is a pain to use with anything other than cmd.exe, this issue is still very much relevant.

[marcelklehr]

The problem is that this introduces a new set of versions.

An option would be to introduce a new version directory in /nodist akin to the x64 dir, i.e. /nodist/v-iojs and add an env var NODIST_IOJS.

This is not ideal, since you can't easily switch between node and iojs. Also, does npm work with iojs?

[marcelklehr]

Scratch that, i gotta think this through.

[marcelklehr]

I will probably create a separate project iodist, which will mirror the features of nodist.

[timdp]

I was kind of planning to do that myself. If you're willing to do it, awesome!

[marcelklehr]

Try https://github.com/marcelklehr/iodist

[robrich]

How to use iodist and nodist at the same time? Must I adjust PATH and NODE_PATH each time?

[einfallstoll]

nodist should integrate iodist. There's no need to separate them.

[marcelklehr]

@robrich A problem is that both tools come with npm. I think using one directory for both node's and iojs' global modules should be possible.

@einfallstoll If you have a good design proposal in mind on how to integrate the two into one tool please enlighten me :)

[einfallstoll]

@marcelklehr I like the approach from https://github.com/tj/n

• delivered through npm
• io.js and node.js support
• doesn't need to uninstall node first

[robrich]

@marcelklehr Would you be open to a pull request that does these two things:

1. Adds command line arg support for --x86, --x64, io, and node:
   nodist add node 0.1.2: install node or io (default to node) version specified
   nodist r --x86 io 1.2.3 -- foo.js: run io (or node) in x86 (or x64) mode, ignoring NODIST_X64 env var
2. Changes the download structure to this:
   • dist (or a better name?)
     • node
       • x86
       • x64
     • io
       • x86
       • x64

[marcelklehr]

Something, I realize now, that's not clear to me: Is iojs.exe supposed to replace node.exe literally? (So you'd still type node, but actually it's io.js running things?) If that's the case I'd happily accept a pull request with @robrich's changes. If not, iodist should work for now, no?

[einfallstoll]

I don't like that by default io.js adds an alias for node. How did TJ do that?

Am 13.04.2015 um 21:18 schrieb Marcel Klehr notifications@github.com:

Something, I realize now, that's not clear to me: Is iojs.exe supposed to replace node.exe literally? (So you'd still type node, but actually it's io.js running things?) If that's the case I'd happily accept a pull request with @robrich's changes. If not, iodist should work for now, no?

—
Reply to this email directly or view it on GitHub.

[AluisioASG]

@marcelklehr Yes; see e.g. nodejs/node#249 (comment) and nodejs/node#631 (comment)

[marcelklehr]

Alright, then. @robrich go for it :)

[hoichi]

Shouldn't iodist links point to robrich/iodist now? Or is it just a temporary fork?

[marcelklehr]

Try out io.js support now. You can see available iojs versions in nodist dist and install them by using the same specs: nodist iojsv2.x

Previously installed node versions under 0.5.x no longer work, you need to rm -rf your version directory (NODIST_PREFIX\v or NODIST_PREFIX\v-x64).