NodeJS版本号混乱 [英] NodeJS version number confusion

查看:111
本文介绍了NodeJS版本号混乱的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

几个月前,我安装了Node JS,并玩了一些.今天,我想开始学习更多有关节点的知识,在编码之前,我决定要确保自己具有最新版本.

I installed Node JS several months ago and played around a bit. Today, I wanted to start learning more about node and before coding, I decided I wanted to make sure I had the latest version.

我检查了版本,它类似于v0.10.3x.我在NodeJS网站上查看,它显示的最新版本为v4.1.0.所以我以为哇!我最好进行升级,而且我简直不敢相信它在短短几个月内就迅速升级到了4.x版本.

I checked the version and it was something like v0.10.3x. I looked on the NodeJS website and it shows the latest version as v4.1.0. So I thought Woahhh! I better upgrade and I couldn't believe it moved that fast to a 4.x version in only a few months.

我花了很多时间试图弄清楚如何完全卸载node和npm,因为我似乎无法对其进行升级.

I spent quite some time trying to figure out how to completely uninstall node and npm because I couldn't seem to upgrade it.

最后我把所有东西都撕了,然后用yum安装在CentOS 7上.我知道我不会通过yum获得最新版本,但是,我认为它已经足够接近了.

Finally I got it all ripped out, then installed in on CentOS 7 using yum. I know I won't get the latest version through yum but, I figured it would be close enough.

安装后,我的电话是v0.10.40.

After install, I am at v0.10.40.

我有种感觉,我对NodeJS版本号一无所知.

I have a feeling I just don't understand something about NodeJS version numbers.

有人可以给我一些启示吗?预先感谢.

Can someone shed some light for me? Thanks in advance.

推荐答案

是的,如果您仅使用官方的node.js运行时,那么它似乎会从0.12.x一直跳到4.0.0. .您可能不知道的是,那些对节点存储库停滞了多少感到厌烦的节点开发人员将这个项目称为io.js.在过去的六个月左右的时间里,该项目以io.js的名义前进.它从v1.x开始,并一直迭代到2.x和3.x.旧的node.js使用了不同的版本控制系统,其中奇数版本是不稳定的,偶数版本是稳定的. Io.js切换为使用 semver 版本控制语义,例如已使用npm上的软件包.

Yeah if you only used the official node.js runtime then it would have appeared to jump from 0.12.x all the way to 4.0.0 in one fell swoop. What you may not have known was that node devs that were sick of how much the node repository was stagnating made a fork of the project and called it io.js. Under the io.js name the project marched forward over the last six months or so; it started at v1.x and iterated all the way through 2.x and 3.x in that time. Old node.js used a different versioning system wherein the odd versions were unstable and even versions were stable. Io.js switched to using semver versioning semantics like packages on npm already use.

经过深思熟虑,Joyent(node.js的原始维护者)终于屈服了,并帮助围绕node成立了一个适当的开放委员会,以与io.js已经进行的相同方式推动该项目前进.几个月前,他们同意将io.js合并回node.js(这是最初创建io.js的人的目标).他们终于在最近完成了两个项目的合并. io.js的名称已不再存在,node.js的生命力始于v4.0.它将继续使用io.js一样的semver语义:)

After a lot of deliberation Joyent (original maintainers of node.js) finally caved in and helped form a proper open committee around node in an effort to push the project forward in much the same way io.js was already doing. A few months ago they agreed to merge io.js back into node.js (which was the goal of those who created io.js in the first place). They finally finished merging the two projects recently. The name io.js is no more and node.js lives on starting at v4.0. It will continue to use semver semantics like io.js did :)

使用node前进会更简单.我很高兴看到项目从这里开始.

Going forward things with node will be MUCH simpler. I'm excited to see where the project goes from here.

这篇关于NodeJS版本号混乱的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆