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

Closed
stelcheck opened this Issue Dec 3, 2014 · 73 comments

Comments

Projects
None yet
@stelcheck
Contributor

stelcheck commented Dec 3, 2014

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

This comment has been minimized.

Show comment
Hide comment
@ronkorving

ronkorving Dec 3, 2014

Contributor

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

Contributor

ronkorving commented Dec 3, 2014

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

@creationix

This comment has been minimized.

Show comment
Hide comment
@creationix

creationix Dec 3, 2014

Owner

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.

Owner

creationix commented Dec 3, 2014

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

This comment has been minimized.

Show comment
Hide comment
@ljharb

ljharb Dec 3, 2014

Collaborator

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.

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@Starefossen

Starefossen Dec 4, 2014

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

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

@fengmk2 fengmk2 referenced this issue in cnpm/cnpmjs.org Dec 6, 2014

Closed

io.js dist #523

@JJ

This comment has been minimized.

Show comment
Hide comment

JJ commented Dec 10, 2014

👍

@waxzce

This comment has been minimized.

Show comment
Hide comment

waxzce commented Dec 10, 2014

+1

@ljharb ljharb referenced this issue in isaacs/nave Dec 10, 2014

Closed

Working with io.js #63

@Nicolab

This comment has been minimized.

Show comment
Hide comment

Nicolab commented Dec 14, 2014

+1

@zxqfox

This comment has been minimized.

Show comment
Hide comment
@zxqfox

zxqfox Dec 31, 2014

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

zxqfox commented Dec 31, 2014

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

@danielb2

This comment has been minimized.

Show comment
Hide comment
@danielb2

danielb2 Jan 8, 2015

Contributor

👍 for supporting both node and io.js

Contributor

danielb2 commented Jan 8, 2015

👍 for supporting both node and io.js

@snostorm

This comment has been minimized.

Show comment
Hide comment

snostorm commented Jan 8, 2015

👍

@fixe

This comment has been minimized.

Show comment
Hide comment

fixe commented Jan 9, 2015

+1!

@fixe

This comment has been minimized.

Show comment
Hide comment

fixe commented Jan 9, 2015

@sdd

This comment has been minimized.

Show comment
Hide comment

sdd commented Jan 9, 2015

👍

@isvissu

This comment has been minimized.

Show comment
Hide comment

isvissu commented Jan 9, 2015

👍

@joshmanders

This comment has been minimized.

Show comment
Hide comment
@joshmanders

joshmanders Jan 10, 2015

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

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

@rcsole

This comment has been minimized.

Show comment
Hide comment

rcsole commented Jan 10, 2015

👍

@Qard

This comment has been minimized.

Show comment
Hide comment
@Qard

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

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

This comment has been minimized.

Show comment
Hide comment
@ljharb

ljharb Jan 12, 2015

Collaborator

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.

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@danielb2

danielb2 Jan 12, 2015

Contributor

Nice! Thanks Jordan ;)

Contributor

danielb2 commented Jan 12, 2015

Nice! Thanks Jordan ;)

@joshmanders

This comment has been minimized.

Show comment
Hide comment

@ljharb You rock!

@DomT4

This comment has been minimized.

Show comment
Hide comment
@DomT4

DomT4 Jan 12, 2015

Contributor

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.

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.

@Joshua-Anderson Joshua-Anderson referenced this issue in travis-ci/travis-ci Jan 13, 2015

Closed

Add io.js runtime #3108

@dmamills

This comment has been minimized.

Show comment
Hide comment
@teabyii

This comment has been minimized.

Show comment
Hide comment

teabyii commented Jan 14, 2015

+1

@kazupon

This comment has been minimized.

Show comment
Hide comment

kazupon commented Jan 14, 2015

+1

@sorrycc

This comment has been minimized.

Show comment
Hide comment

sorrycc commented Jan 14, 2015

👍

@dougwilson dougwilson referenced this issue in nodejs/node Jan 14, 2015

Closed

Travis CI #364

@chicoxyzzy

This comment has been minimized.

Show comment
Hide comment
@chicoxyzzy

chicoxyzzy Jan 14, 2015

👍 wanna harmony of server-side js 🙏

👍 wanna harmony of server-side js 🙏

@ericelliott

This comment has been minimized.

Show comment
Hide comment
@ericelliott

ericelliott Jan 14, 2015

👍 @ljharb that's great news! =)

👍 @ljharb that's great news! =)

@hemanth

This comment has been minimized.

Show comment
Hide comment

hemanth commented Jan 14, 2015

👍 @ljharb++ :)

@ksheedlo

This comment has been minimized.

Show comment
Hide comment
@ksheedlo

ksheedlo Jan 14, 2015

👍

For the sake of usability, though, I'd rather not call it ivm. That's too easy to type when trying for vim :) I'm playing with io.js and the builtin environment variables right now and iovm rolls off the keyboard pretty nicely. Just a suggestion.

👍

For the sake of usability, though, I'd rather not call it ivm. That's too easy to type when trying for vim :) I'm playing with io.js and the builtin environment variables right now and iovm rolls off the keyboard pretty nicely. Just a suggestion.

@ljharb

This comment has been minimized.

Show comment
Hide comment
@ljharb

ljharb Jan 14, 2015

Collaborator

The name will remain nvm.

Collaborator

ljharb commented Jan 14, 2015

The name will remain nvm.

@ksheedlo

This comment has been minimized.

Show comment
Hide comment
@ksheedlo

ksheedlo Jan 14, 2015

@ljharb +1, that's probably the best thing to do.

@ljharb +1, that's probably the best thing to do.

@halfdan

This comment has been minimized.

Show comment
Hide comment

halfdan commented Jan 14, 2015

+1

@pose

This comment has been minimized.

Show comment
Hide comment

pose commented Jan 14, 2015

👍

@acdlite

This comment has been minimized.

Show comment
Hide comment

acdlite commented Jan 14, 2015

+1

@hirofumii

This comment has been minimized.

Show comment
Hide comment

+1

@bweston92

This comment has been minimized.

Show comment
Hide comment

+1 ;)

@sergeybe

This comment has been minimized.

Show comment
Hide comment

+1

@DavidSouther

This comment has been minimized.

Show comment
Hide comment
@DavidSouther

DavidSouther Jan 14, 2015

PSA: There are over 30 +1s and thumbs up for this issue. iojs beta was released not 10 hours ago (from the time of this comment). The discussions here and elsewhere have been unanimous: nvm WILL support iojs, it will be called iojs, and will you please stop spamming this list and have just a bit of patience for this to make it in to nvm with appropriate testing, etc?

PSA: There are over 30 +1s and thumbs up for this issue. iojs beta was released not 10 hours ago (from the time of this comment). The discussions here and elsewhere have been unanimous: nvm WILL support iojs, it will be called iojs, and will you please stop spamming this list and have just a bit of patience for this to make it in to nvm with appropriate testing, etc?

@poying

This comment has been minimized.

Show comment
Hide comment

poying commented Jan 14, 2015

+1

@mahnunchik

This comment has been minimized.

Show comment
Hide comment

👍

@clebert

This comment has been minimized.

Show comment
Hide comment

clebert commented Jan 14, 2015

+1

@zeke

This comment has been minimized.

Show comment
Hide comment

zeke commented Jan 14, 2015

yep

@deini

This comment has been minimized.

Show comment
Hide comment

deini commented Jan 14, 2015

👍

@fengmk2

This comment has been minimized.

Show comment
Hide comment

fengmk2 commented Jan 15, 2015

👍

@denji

This comment has been minimized.

Show comment
Hide comment

denji commented Jan 15, 2015

👍

@vvakame

This comment has been minimized.

Show comment
Hide comment

vvakame commented Jan 15, 2015

👍

@hallas

This comment has been minimized.

Show comment
Hide comment

hallas commented Jan 15, 2015

👍

@kriswill

This comment has been minimized.

Show comment
Hide comment
@kriswill

kriswill Jan 15, 2015

Maybe this #610 will help =)

Maybe this #610 will help =)

@ljharb

This comment has been minimized.

Show comment
Hide comment
@ljharb

ljharb Jan 15, 2015

Collaborator

@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!

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@stelcheck

stelcheck Jan 15, 2015

Contributor

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

Contributor

stelcheck commented Jan 15, 2015

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

@Anachron Anachron referenced this issue in dbashford/mimosa Jan 15, 2015

Open

Support for IO.JS #423

@ljharb ljharb added io.js and removed needs followup labels Jan 16, 2015

@springmeyer springmeyer referenced this issue in mapbox/node-sqlite3 Jan 17, 2015

Closed

Support building io.js binaries on appveyor and travis #390

2 of 2 tasks complete

fengmk2 pushed a commit to fengmk2/nvmw that referenced this issue Jan 17, 2015

苏千
Add io.js support and download npm from github
Install iojs just like nvm does, creationix/nvm#590

    nvmw install iojs/1.0.2
    nvmw use iojs/1.0.2

Fixes #30 #27

fengmk2 pushed a commit to fengmk2/nvmw that referenced this issue Jan 17, 2015

苏千
Add io.js support and download npm from github
Install iojs just like nvm does, creationix/nvm#590

    nvmw install iojs/1.0.2
    nvmw use iojs/1.0.2

Fixes #30 #27

fengmk2 added a commit to fengmk2/nvmw that referenced this issue Jan 17, 2015

Add io.js support and download npm from github
Install iojs just like nvm does, creationix/nvm#590

    nvmw install iojs/1.0.2
    nvmw use iojs/1.0.2

Fixes #30 #27

fengmk2 added a commit to fengmk2/nvmw that referenced this issue Jan 17, 2015

Add io.js support and download npm from github
Install iojs just like nvm does, creationix/nvm#590

    nvmw install iojs/1.0.2
    nvmw use iojs/1.0.2

Fixes #30 #27

fengmk2 added a commit to fengmk2/nvmw that referenced this issue Jan 18, 2015

Add io.js support and download npm from github
Install iojs just like nvm does, creationix/nvm#590

    nvmw install iojs/1.0.2
    nvmw use iojs/1.0.2

Fixes #30 #27

fengmk2 added a commit to fengmk2/nvmw that referenced this issue Jan 18, 2015

Add io.js support and download npm from github
Install iojs just like nvm does, creationix/nvm#590

    nvmw install iojs/1.0.2
    nvmw use iojs/1.0.2

Fixes #30 #27

@ljharb ljharb referenced this issue Jan 19, 2015

Merged

`io.js` support #616

@bajtos bajtos referenced this issue in node-inspector/node-inspector Jan 19, 2015

Merged

Fix --hidden option for NODE_DEBUG mode #530

@ljharb ljharb closed this in #616 Jan 20, 2015

ljharb added a commit that referenced this issue Jan 20, 2015

Merge pull request #616 from ljharb/iojs
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

This comment has been minimized.

Show comment
Hide comment
@stelcheck

stelcheck Jan 20, 2015

Contributor

Thank you!

Contributor

stelcheck commented Jan 20, 2015

Thank you!

@waxzce

This comment has been minimized.

Show comment
Hide comment
@waxzce

waxzce Jan 20, 2015

thx indeed

waxzce commented Jan 20, 2015

thx indeed

@ghost

This comment has been minimized.

Show comment
Hide comment

ghost commented Jan 20, 2015

thx :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment