Node.js 版本
¥Node.js Releases
主要 Node.js 版本进入当前发布状态六个月,这让库作者有时间添加对它们的支持。六个月后,奇数版本(9、11 等)将不再受支持,偶数版本(10、12 等)将转为 Active LTS 状态并可供一般使用。LTS 发布状态为 "长期支持",通常可保证在总共 30 个月内修复关键错误。生产应用应仅使用 Active LTS 或维护 LTS 版本。
¥Major Node.js versions enter Current release status for six months, which gives library authors time to add support for them. After six months, odd-numbered releases (9, 11, etc.) become unsupported, and even-numbered releases (10, 12, etc.) move to Active LTS status and are ready for general use. LTS release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months. Production applications should only use Active LTS or Maintenance LTS releases.
发布时间表
¥Release Schedule
有关 Node.js 发布时间表的完整详细信息可在 在 GitHub 上 中找到。
¥Full details regarding the Node.js release schedule are available on GitHub.
商业支持
¥Commercial Support
通过我们的 OpenJS 生态系统可持续发展计划合作伙伴 HeroDevs,可以获得维护阶段之后版本的商业支持。
¥Commercial support for versions past the Maintenance phase is available through our OpenJS Ecosystem Sustainability Program partner HeroDevs.
正在寻找版本分支的最新版本?
¥Looking for the latest release of a version branch?
Node.js | 代号 | 首次发布 | 上次更新 | 状态 | |
---|---|---|---|---|---|
v24 | - | Current | 详情 | ||
v23 | - | Maintenance | 详情 | ||
v22 | Jod | LTS | 详情 | ||
v21 | - | End-of-life | 详情 | ||
v20 | Iron | Maintenance | 详情 | ||
v19 | - | End-of-life | 详情 | ||
v18 | Hydrogen | End-of-life | 详情 | ||
v17 | - | End-of-life | 详情 | ||
v16 | Gallium | End-of-life | 详情 | ||
v15 | - | End-of-life | 详情 | ||
v14 | Fermium | End-of-life | 详情 | ||
v13 | - | End-of-life | 详情 | ||
v12 | Erbium | End-of-life | 详情 | ||
v11 | - | End-of-life | 详情 | ||
v10 | Dubnium | End-of-life | 详情 | ||
v9 | - | End-of-life | 详情 | ||
v8 | Carbon | End-of-life | 详情 | ||
v7 | - | End-of-life | 详情 | ||
v6 | Boron | End-of-life | 详情 | ||
v5 | - | End-of-life | 详情 | ||
v4 | Argon | End-of-life | 详情 | ||
v0 | - | End-of-life | 详情 |
官方安装方法与社区安装方法
¥Official vs. Community Installation Methods
Node.js 网站提供了几种非交互式安装方法,包括命令行接口 (CLI)、操作系统 (OS) 软件包管理器(例如 brew
)和 Node.js 版本管理器(例如 nvm
)。
¥The Node.js website provides several non-interactive installation methods, including command-line interfaces (CLIs), operating system (OS) package managers (e.g., brew
), and Node.js version managers (e.g., nvm
).
为了突出和推广社区贡献,Node.js 项目引入了修订版的“下载”页面,将安装方式分为“官方”或“社区”。这为用户提供了更大的灵活性和选择。为了确保清晰,我们为每个类别定义了标准。
¥To highlight and promote community contributions, the Node.js project introduced a revised Downloads page categorizing installation methods as either “Official” or “Community.” This provides users with increased flexibility and choice. To ensure clarity, we’ve defined criteria for each category.
官方安装方法
¥Official Installation Methods
标记为“官方”的安装方法必须满足以下要求:
¥Installation methods designated as “Official” must meet the following requirements:
要求(官方安装方法) |
---|
新的 Node.js 版本必须与官方版本同时发布。 |
项目维护者必须与 Node.js 项目保持密切联系,包括建立直接沟通渠道。 |
安装方法必须下载 Node.js 项目打包的官方二进制文件。 |
当有预编译的二进制文件可用时,安装方法不得从源代码构建,也不得修改官方二进制文件。 |
社区安装方法
¥Community Installation Methods
自助下载页面 (/download) 上的社区安装方法也必须遵循一组最低标准:
¥Community installation methods included on the self-service download page (/download) must also adhere to a minimum set of criteria:
-
版本支持:必须支持所有当前支持的、非生命周期结束 (EOL) 的 Node.js 版本。
¥Version Support: Must support all currently supported, non-End-of-Life (EOL) Node.js versions.
-
操作系统兼容性:必须至少在一个官方支持的操作系统 (OS) 上运行。
¥OS Compatibility: Must function on at least one officially supported Operating System (OS).
-
广泛的操作系统支持:不能仅限于部分操作系统发行版或版本。
¥Broad OS Support: Cannot be limited to a subset of OS distributions or versions.
-
例如,声称与“Windows”兼容的安装方法必须能够在“Windows 10”、“Windows 11”及其所有版本(包括服务器版本)上运行。
¥For example, an installation method claiming compatibility with “Windows” must function on “Windows 10”, “Windows 11”, and all their editions (including server versions).
-
同样,声称与“Linux”兼容的安装方法必须可安装在所有主流 Linux 发行版上,而不仅仅是特定的子集。它不能依赖于特定于发行版的包管理器,例如
apt
或dnf
。¥Similarly, an installation method claiming compatibility with “Linux” must be installable on all major Linux distributions, not just a specific subset. It cannot rely on distribution-specific package managers like
apt
ordnf
.
-
-
免费开源:必须免费使用且开源,不得作为商业产品出售,也不得是付费服务。
¥Free and Open Source: Must be free to use and open source, must not be sold as a commercial product, and must not be a paid service.