未加星标

Node.js v6 Transitions to LTS

字体大小 | |
[前端(javascript) 所属分类 前端(javascript) | 发布者 店小二04 | 时间 2016 | 作者 红领巾 ] 0人收藏点击收藏
Node.js v7 will become a current release line. Node.js v6, code named “Boron,” transitions to LTS. Node.js v0.10 will reach “End of Life” at the end of the month. There will be no further releases of this line, including security or stability patches.

Node.js v6 transitioned to LTS line today , so let’s talk about what this means, where other versions stand, and what to expect with Node.js v7.

Node.js Project’s LTS Strategy

In a nutshell, the Long Term Support (LTS) strategy is focused on creating stability and security to organizations with complex environments that find it cumbersome to continually upgrade Node.js. These release lines are even numbered and are supported for 30 months ― more information on the LTS strategy can be found here .


Node.js v6 Transitions to LTS

*This image is under copyright of NodeSource.

Another good source for the history and strategy of the Node.js release lines, can be found in Rod Vagg’s blog post, “ Farewell to Node.js v5, Preparing for Node.js v7 .” Rod is the Node.js Project’s technical steering committee director and a Node.js Foundation board member.

Node.js follows semantic versioning (semver). Essentially, semver is how we signal how changes will affect the software, and whether or not upgrading will “break” software to help developers determine whether they should download a new version, and when they should download a new version. There is a simple set of rules and requirements that dictate how version numbers are assigned and incremented, and whether they fall into the following categories:

Patch Release: Is a bug fix or a small improvement to performance. It doesn’t add new features or change the way the software works. Patches are an easy upgrade. Minor Release: This is any change to the software that introduces new features, but does not change the way that the software works. Given that there is a new feature being release, it is generally best to wait to upgrade to a minor release after it has been tested and patched. Major Release: This is a big breaking change. It changes how the software works and functions. With Node.js, it can be as simple as changing an error message to upgrading V8.

If you want more information on how releases work, watch Myles Borins’ presentation at JSConf Uruguay: https://www.youtube.com/watch?v=5un1I2qkojg. Myles is a member of the Node.js Project and Node.js Core Technical Committee.

Node.js v6 Moves from “Current” to “LTS”

Node.js v6 will be the LTS release line until April 2018, meaning new features ( semver -minor) may only land with consent of the Node.js project’s Core Technical Committee and the LTS Working Group. These features will land on an infrequent basis.

Changes in a LTS-covered major version are limited to:

Bug fixes; Security updates; Non-semver-major npm updates; Relevant documentation updates; Certain performance improvements where the risk of breaking existing applications is minimal; Changes that introduce a large amount of code churn where the risk of breaking existing applications is low and where the change in question may significantly ease the ability to backport future changes due to the reduction in diff noise.

After April 2018, Node.js v6 will transition into “maintenance” mode for 12 additional months. Maintenance mode means that only critical bugs, critical security fixes, and documentation updates will be permitted.

Node.js v6 is important to enterprises and users that need stability.If you have a large production environment and need to keep Node.js humming, then you want to be on an LTS release line. If you fall within this category, we suggest that you update to Node.js v6, especially if you are on v0.10 or v0.12. *More information on this as well as what to do if you are on Node.js v4 below.

Features, Focus and More Features

Node.js v6 became a current release line in April 2016 . Its main focus is on performance improvements, increased reliability and better security. A few notable features and updates include:

Security Enhancements New Buffer API creation for increased safety and security. Experimental support for the “v8_inspector,” a new experimental debugging protocol. *If you have an environment that cannot handle updates or testing, do not try this new feature as it is not fully supported and could have bugs. Increased Reliability Print warning to standard error when a native Promise rejection occurs, but there is no handler to receive it. This is particularly important for distributed teams building applications. Before this capability, they would have to chase down the problem, which is equivalent to finding a needle in a haystack. Now, they can easily pinpoint where the problem is and solve it. Performance Improvements Support of V8 javascript engine 5.1, which includes default function parameters , destructuring , and rest parameters to name a few. You can view the full list of features here . Ninety-seven percent of ES6 features are now supported by Node.js v6. Node.js v6 Equipped with npm v3 Npm3 resolves dependencies differently than npm2 in that it tries to mitigate the deep trees and redundancy that nesting causes in npm2 ― more on this can be found in npm’s blog post on the subject . The flattened dependency tree will be very important in particular to windows users who have file path length limitations. In addition, npm’s shrinkwrap functionality has changed. The updates will provide a more consistent way to stay in sync with package.json when you use the save flag or adjust dependencies. Users who deploy projects using shrinkwrap consistently (most enterprises do) should watch for changes in behaviour. Updating Node.js v4 to Node.js v6

If you are on Node.js v4, you have 18 months to transition from Node.js v4 to Node.js v6. We suggest starting now. Node.js v4 will stop being maintained April 2018.

At the current rate of download , Node.js v6 will take over the current LTS line v4 in downloads by the end of the year. This is a good thing as v6 will be the LTS line and in maintenance mode for the next 30

本文前端(javascript)相关术语:javascript是什么意思 javascript下载 javascript权威指南 javascript基础教程 javascript 正则表达式 javascript设计模式 javascript高级程序设计 精通javascript javascript教程

主题: Node.jsJavaScriptJavaWindows
分页:12
转载请注明
本文标题:Node.js v6 Transitions to LTS
本站链接:http://www.codesec.net/view/484707.html
分享请点击:


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 前端(javascript) | 评论(0) | 阅读(25)