Announcement: Node.js 14 and 16 End-of-Life Dates

[jshackell-sfdc]

If you install Salesforce CLI using npm, and use Node.js 14 or 16, be aware of these end-of-life announcements.

NOTE: If you install Salesforce CLI using the installers (.pkg, .exe, or TAR files), these announcements don't apply to you. Salesforce CLI installers and TAR files bundle the LTS version of Node.js, so keeping Salesforce CLI updated to its latest release also keeps you current with Node.js.

Node.js 14 End-of-Life

The end-of-life date for Node.js 14 is April 30, 2023.

We’ll start modifying Salesforce CLI plugins and libraries to require Node.js 16 or higher in early May 2023. We’ll be taking advantage of new syntax features that don’t work on Node.js 14.

Node.js recommends that if you’re using Node.js 14, move to Node.js 18 and not Node.js 16, because the latter has such a short remaining lifespan.

Node.js 16 End-of-Life (Brought Forward)

The end-of-life date for Node.js 16 is September 11, 2023. This date is earlier than previously published.

Node.js’s blog explains why they chose this earlier end-of-life date.

When Node.js drops support for Node.js 16, Salesforce CLI will too.

Salesforce Recommendations

Generally, we recommend using Node.js 18.

If you're unable to change your Node.js version to a supported version, we recommend that you install Salesforce CLI from a TAR file or installer. Your computer can then have the older Node.js version installed, but Salesforce CLI will bring its own supported Node.js version and not use the one on your computer.

If you're using the sfdx-lwc-jest plugin package, please see this issue around the impact of node versions, a known bug in its jest dependency, and various tradeoffs/workarounds.

[github-actions]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[AllanOricil]

@jshackell-sfdc

This issue affects this decision depending on the amount of tests developers have in their projects. You have to upgrade Jest to v29 if you want to support node > 16.10

[jshackell-sfdc]

@mshanemc , can you respond to Allan's comment above? Thx.

[jshackell-sfdc]

@AllanOricil , thanks for letting us know about that issue. We updated our announcement accordingly.

[AllanOricil]

14 and 16 are forever part of my life. I will miss them 😭