Announcement: Dropping support for Node.js 18 and 20

[WillieRuemmele]

Node.js 18 reached End-of-Life in September 2025 and Node.js 20 reached End-of-Life in April 2026. Starting with an upcoming release, Salesforce CLI will require Node.js >= 22.

What's changing

• The engines.node field across all CLI packages will be updated from >=18.0.0 to >=22.0.0
• npm install on Node < 22 will produce an engines compatibility warning
• Runtime behavior on Node 18/20 is already broken due to upstream dependency changes (see @salesforce/core declares Node >=18 but resolves @jsforce/jsforce-node >=3.10.17 which requires Node >=22 — runtime crash on Node 18/20 #3596)

Who is affected

Users running Salesforce CLI on Node.js 18 or 20, whether installed via npm or running plugins that depend on @salesforce/core.

Alternatives

If you cannot upgrade to Node.js 22 or 24 immediately:

• Pin to your current CLI version: npm install -g @salesforce/cli@2.141.6 (last version before the engines bump)
• Use an older tarball: Download from the CLI releases page — tarballs prior to this change bundle Node 22 and will continue to function
• Use nvm or fnm to manage multiple Node versions and switch to 22+ for CLI usage

Recommended action

Upgrade to Node.js 24 (Current LTS) or Node.js 22 (Maintenance LTS until April 2027):

# Using nvm
nvm install 24
nvm use 24

# Using fnm
fnm install 24
fnm use 24

Timeline

• Node 18 EOL: September 2025
• Node 20 EOL: April 2026
• Node 22 Maintenance LTS: until April 2027
• Node 24 Active LTS: until April 2028

See Node.js release schedule for details.

Related

• @salesforce/core declares Node >=18 but resolves @jsforce/jsforce-node >=3.10.17 which requires Node >=22 — runtime crash on Node 18/20 #3596 — @salesforce/core already crashes on Node 18/20 due to @jsforce/jsforce-node requiring Node >= 22
• Announcement: upcoming update to Node.js v24 #3445 — Bundled Node.js version updated to v24 in installers/tarballs