Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

io.js support #72

Closed
timdp opened this issue Jan 14, 2015 · 21 comments
Closed

io.js support #72

timdp opened this issue Jan 14, 2015 · 21 comments
Milestone

Comments

@timdp
Copy link

timdp commented Jan 14, 2015

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

@robertd
Copy link

robertd commented Jan 15, 2015

+1

@unlight
Copy link

unlight commented Jan 16, 2015

+2

@AriaMinaei
Copy link

+1

1 similar comment
@ForbesLindesay
Copy link

+1

@timdp
Copy link
Author

timdp commented Feb 5, 2015

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
Copy link
Member

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
Copy link
Member

Scratch that, i gotta think this through.

@marcelklehr
Copy link
Member

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

@timdp
Copy link
Author

timdp commented Feb 12, 2015

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

@marcelklehr
Copy link
Member

@robrich
Copy link
Collaborator

robrich commented Mar 21, 2015

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

@einfallstoll
Copy link
Contributor

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

@marcelklehr
Copy link
Member

@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
Copy link
Contributor

@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
Copy link
Collaborator

robrich commented Apr 6, 2015

@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
Copy link
Member

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
Copy link
Contributor

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
Copy link

@marcelklehr
Copy link
Member

Alright, then. @robrich go for it :)

@hoichi
Copy link

hoichi commented Apr 23, 2015

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

@marcelklehr marcelklehr modified the milestone: 0.6 Jul 13, 2015
@marcelklehr
Copy link
Member

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants