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, node-forward: should/will NVM support more than node? #590

Closed
stelcheck opened this issue Dec 3, 2014 · 73 comments · Fixed by #616
Closed

IO.js, node-forward: should/will NVM support more than node? #590

stelcheck opened this issue Dec 3, 2014 · 73 comments · Fixed by #616
Assignees
Labels
feature requests I want a new feature in nvm! io.js This relates to https://iojs.org/

Comments

@stelcheck
Copy link
Contributor

Notice

There are no need for additional +1 or pretty pleases. @ljharb is already working on it, and all you are doing by +1'ing is spamming a whole bunch of people.

Further more, it has been mentioned that no contributions are required at this time for the implementation of this feature.

So let's all keep quiet for a while, and give a chance to @ljharb to finish his work :)


I know it is very early to start the conversation on this matter, but with a potential first release by IO.js coming up in little over a month, I thought it might be an interesting conversation to have.

At this point, NVM manages, well, Node.js versions. However, nodejs/node#28 already started to discuss ideas like aliasing node and so on. I would be against that idea in general, but in the context of NVM, it might just make sense: after all, you explicitly pick a node version, and are told about the one you will want to use.

Anyway, the core idea is: if we are to see node forks, how about managing them too?

nvm install node/v0.10.33
nvm install iojs/v1.0.0-alpha
nvm install hypotheticalnode/v1.2.3

Doing so - and again, perhaps auto-alias commands? - could make it very nice for developers; keep the same old habits, just change your node version.

TBH I am not sure if it's that good of an idea in the first place, but it's probably one that ought to be interesting to discuss.

@ronkorving
Copy link

It's that, or perhaps fork it to ivm (io.js version manager)?

@creationix
Copy link
Collaborator

FWIW I was about to propose the same thing here. I think renaming to ivm is a little premature since most people still think of the project in terms of "node". Heck I still think of MariaDB as that MySQL thing and LibreOffice as OpenOffice.

@ljharb
Copy link
Member

ljharb commented Dec 3, 2014

It's way way too early. No further discussion is required at this time.

This project will keep its name for the foreseeable future, whether it adds support for an arbitrary fork of node.js or not.

If the community starts moving in a major way towards any given fork of node, and if that fork provides the same installation methods that node does (binaries and source), then this project should be able to easily support it, and I'd intend to do so. However, the mere existence of a node fork with high-profile committers should in no way change the direction of an established project such as this one.

@Starefossen
Copy link

Yes, an IO.js install option would be great!

@JJ
Copy link

JJ commented Dec 10, 2014

👍

1 similar comment
@waxzce
Copy link

waxzce commented Dec 10, 2014

+1

@Nicolab
Copy link

Nicolab commented Dec 14, 2014

+1

@ljharb ljharb added the needs followup We need some info or action from whoever filed this issue/PR. label Dec 17, 2014
@qfox
Copy link

qfox commented Dec 31, 2014

+1 Let's wait Fedor's birthday. Happy new year, guys! 🎄

@danielb2
Copy link
Contributor

danielb2 commented Jan 8, 2015

👍 for supporting both node and io.js

@snostorm
Copy link

snostorm commented Jan 8, 2015

👍

@fixe
Copy link

fixe commented Jan 9, 2015

+1!

@fixe
Copy link

fixe commented Jan 9, 2015

Refs nodejs/node#43.

@sdd
Copy link

sdd commented Jan 9, 2015

👍

1 similar comment
@isvissu
Copy link

isvissu commented Jan 9, 2015

👍

@joshmanders
Copy link

Just started using nvm and quite enjoy it. Would love a io.js supported version.

@iamricard
Copy link

👍

@Qard
Copy link

Qard commented Jan 12, 2015

👍

io.js v1.0.0 lands tomorrow. It'd be good to have a version manager that supports it. I write instrumentation, so I have to support it.

@ljharb ljharb self-assigned this Jan 12, 2015
@ljharb
Copy link
Member

ljharb commented Jan 12, 2015

Work on io.js support is in progress. It may or may not land by the time the release is out — for now, please continue to install manually — but expect seamless support to be released soon.

@danielb2
Copy link
Contributor

Nice! Thanks Jordan ;)

@joshmanders
Copy link

@ljharb You rock!

@DomT4
Copy link
Contributor

DomT4 commented Jan 12, 2015

Glad to hear support for io.js is coming 👍. I've been having nightmares for weeks trying to work out how to package the darn thing alongside node without breaking everything. I'm pretty convinced at this point the most sane method is just to use a version manager to switch between the Node-esque projects.

@dmamills
Copy link

@teabyii
Copy link

teabyii commented Jan 14, 2015

+1

@zeke
Copy link

zeke commented Jan 14, 2015

yep

@deini
Copy link

deini commented Jan 14, 2015

👍

4 similar comments
@fengmk2
Copy link

fengmk2 commented Jan 15, 2015

👍

@denji
Copy link

denji commented Jan 15, 2015

👍

@vvakame
Copy link

vvakame commented Jan 15, 2015

👍

@hallas
Copy link

hallas commented Jan 15, 2015

👍

@kriswill
Copy link

Maybe this #610 will help =)

@ljharb
Copy link
Member

ljharb commented Jan 15, 2015

@kriswill That's not sufficient and conflicts with the approach I'm already taking. No further +1's are needed on this issue, and no contributions are necessary. Thanks!

@stelcheck
Copy link
Contributor Author

I just edited the original content of the issue to add a notice asking everyone to quiet down with the +1's. Hopefully that will help :)

@ljharb ljharb added io.js This relates to https://iojs.org/ and removed needs followup We need some info or action from whoever filed this issue/PR. labels Jan 16, 2015
fengmk2 added a commit to fengmk2/nvmw that referenced this issue Jan 17, 2015
Install iojs just like nvm does, nvm-sh/nvm#590

    nvmw install iojs/1.0.2
    nvmw use iojs/1.0.2

Fixes hakobera#30 hakobera#27
fengmk2 added a commit to fengmk2/nvmw that referenced this issue Jan 17, 2015
Install iojs just like nvm does, nvm-sh/nvm#590

    nvmw install iojs/1.0.2
    nvmw use iojs/1.0.2

Fixes hakobera#30 hakobera#27
fengmk2 added a commit to fengmk2/nvmw that referenced this issue Jan 17, 2015
Install iojs just like nvm does, nvm-sh/nvm#590

    nvmw install iojs/1.0.2
    nvmw use iojs/1.0.2

Fixes hakobera#30 hakobera#27
fengmk2 added a commit to fengmk2/nvmw that referenced this issue Jan 17, 2015
Install iojs just like nvm does, nvm-sh/nvm#590

    nvmw install iojs/1.0.2
    nvmw use iojs/1.0.2

Fixes hakobera#30 hakobera#27
fengmk2 added a commit to fengmk2/nvmw that referenced this issue Jan 18, 2015
Install iojs just like nvm does, nvm-sh/nvm#590

    nvmw install iojs/1.0.2
    nvmw use iojs/1.0.2

Fixes hakobera#30 hakobera#27
fengmk2 added a commit to fengmk2/nvmw that referenced this issue Jan 18, 2015
Install iojs just like nvm does, nvm-sh/nvm#590

    nvmw install iojs/1.0.2
    nvmw use iojs/1.0.2

Fixes hakobera#30 hakobera#27
@ljharb ljharb mentioned this issue Jan 19, 2015
ljharb added a commit that referenced this issue Jan 20, 2015
Add `io.js` support.

This branch adds support for https://github.com/iojs/io.js / https://iojs.org/

The following features should now work:
 - `nvm install iojs` will install the latest `io.js` version. `nvm ls iojs` and `nvm use iojs` will function as you'd expect.
 - `nvm install node` will install the latest stable `node` version. `nvm ls node` and `nvm use node` will function as you'd expect.
 - In general, a specific `io.js` version can be referenced with the "iojs-" prefix. If `node` were to ever release a `v1.0.0`, `v1.0.0` would refer to `node`, and `iojs-v1.0.0` would refer to `io.js`. In the near future, `node-v1.0.0` will also refer to `node` unambiguously. This applies to all `nvm` commands, including working with aliases and `.nvmrc` files.
 - `io.js`, unlike `node`, does not have a SunOS binary. Please open an issue on https://github.com/iojs/io.js if this is actually a problem for anyone, as currently it seems like this won't be for anybody.

**Note**: checksum support upon installation is currently disabled. Relates to nodejs/node#368.
**Note**: installation of `io.js` directly from source (via the `-s` option) is not yet enabled. This will be added soon.

Relates to nodejs/node#40 nodejs/node#420
Fixes #590
@stelcheck
Copy link
Contributor Author

Thank you!

@waxzce
Copy link

waxzce commented Jan 20, 2015

thx indeed

@ghost
Copy link

ghost commented Jan 20, 2015

thx :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature requests I want a new feature in nvm! io.js This relates to https://iojs.org/
Projects
None yet
Development

Successfully merging a pull request may close this issue.