It also applies to those who deal with sensitive data such as personally identifiable information (PII). Compliance issues – This risk applies most to teams in highly regulated industries such as healthcare, finance, or ecommerce.If you don’t upgrade to a newer release line, you miss out on features and improvements that enable you to write better, more performant applications. “Boron” users can’t take advantage of this feature. For example, the popular async/await pattern to interact with promises was first introduced in the Node.js 8 (“Carbon”) release line. Software incompatibility – Newer versions of Node.js better support current best practices and newer design patterns. After April 30, security releases will no longer be applied to Node.js 6, increasing the potential for malicious attacks. In the February 2019 Security Release, all actively maintained Node.js release lines were patched, including “Boron”. Security vulnerabilities – Node.js contributors are constantly working to fix security flaws of all severity levels (low, moderate, and high). Continued use of the Node.js 6 runtime after Apincreases your exposure to various risks, including the following: Requests for feature additions to this release line aren’t accepted. This is because language runtimes that have reached EOL are unsupported in Lambda. Recently, AWS has been reminding users to upgrade AWS Lambda functions built on the Node.js 6 runtime to a newer version. This includes releases that address critical bugs, security fixes, patches, or other important updates. After the maintenance period ends, Node.js 6 will no longer be included in Node.js releases. Node.js 6.x (“Boron”), which has been maintained as a long-term stable (LTS) release line since fall of 2016, is reaching its scheduled end-of-life (EOL) on April 30, 2019. This blog was authored by Liz Parody, Developer Relations Manager at NodeSource.
0 Comments
Leave a Reply. |