After v12 will no longer be supported and the oldest supported version will be v14.Node.js 17 will be supported between around to around.After v15 will no longe be supported, but v12 and v14 will continue to be supported.Node.js 16 will be supported between around to around.After v10 will no longer be supported and the oldest supported version will be v12.Node.js 15 will be supported between around to around.After v13 will no longer be supported, but v10 and v12 will continue to be supported.Node.js 14 will be supported between around to around.After v8 will no longer be supported and the oldest supported version will be v10.
Node.js 13 will be supported between around to around. Node.js 12 will be supported between around to around. Node.js 11 will be supported between around to around. Node.js 10 will be supported between around to around. Node.js 9 will be supported between around to around. Node.js 8 will be supported between to around. As of the oldest supported version is v8. We will always have hard support for the latest version. This is an estimate and may change based on the Node.js release cycle. The following predicts our support cycle until 2023. We validate our support for Node.js by running Continuous Integration testing our projects in the latest release of every major version - for example at the time of writing the current LTS release version is 10.16.0 we will test this version but none of the earlier releases in the 10.x.x branch. Any version that is marked "End of Life" we do not officially support, but we will continue to support any version marked as "Maintainence" or "Active". We follow this support cycle by supporting everything from the oldest release still in Maintainence to the current release. Node.js' release cycle is documented here - which can be effectively summarised as: even numbered versions (8, 10, 12, 14) are supported from their date of release for around 3 years, while odd versions (9, 11, 13, 15) are supported for around 6 months. We support Node.js, following its LTS policy. Any actively supported older versions will be documented in the respective projects readme file. We will not actively support older versions unless a negotiation with a third party has been made. As soon as a new release of any project is made, older versions of that project are considered end-of-life. We can only provide support for the latest version of any of our projects. 
To ensure a consistent level of compatibility & support in our projects, each project under the Chai organisation must strictly adhere to a standardised lifecycle support policy, and platform support policy, as documented below.
0 kommentar(er)
