-
-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
Comments
It's that, or perhaps fork it to ivm (io.js version manager)? |
FWIW I was about to propose the same thing here. I think renaming to |
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 If the community starts moving in a major way towards any given fork of |
Yes, an IO.js install option would be great! |
👍 |
1 similar comment
+1 |
+1 |
+1 Let's wait Fedor's birthday. Happy new year, guys! 🎄 |
👍 for supporting both node and io.js |
👍 |
+1! |
Refs nodejs/node#43. |
👍 |
1 similar comment
👍 |
Just started using |
👍 |
👍 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. |
Work on |
Nice! Thanks Jordan ;) |
@ljharb You rock! |
Glad to hear support for |
+1 |
yep |
👍 |
4 similar comments
👍 |
👍 |
👍 |
👍 |
Maybe this #610 will help =) |
@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! |
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 :) |
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
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
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
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
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
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
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
Thank you! |
thx indeed |
thx :) |
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?
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.
The text was updated successfully, but these errors were encountered: