Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
IO.js, node-forward: should/will NVM support more than node? #590
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
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.
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
referenced this issue
Dec 3, 2014
Glad to hear support for
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: