Skip to content

fix: drop Node 18/20 support, require >=22 @W-23388103@#178

Closed
WillieRuemmele wants to merge 1 commit into
mainfrom
wr/dropNode18And20Support
Closed

fix: drop Node 18/20 support, require >=22 @W-23388103@#178
WillieRuemmele wants to merge 1 commit into
mainfrom
wr/dropNode18And20Support

Conversation

@WillieRuemmele

@WillieRuemmele WillieRuemmele commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Bump engines.node from >=18.0.0 to >=22.0.0
  • Node 18 reached EOL September 2025, Node 20 reached EOL April 2026
  • Fresh installs already crash on Node 18/20 due to @jsforce/jsforce-node@3.10.17 pulling undici@^8.5.0 (requires Node >=22)

Fixes forcedotcom/cli#3596
Related forcedotcom/cli#3603

Work Item

@W-23388103@: [CLI] Use node v24, deprecate 18 and 20

Test plan

  • CI passes on Node 22 and 24 (already the case — CI hasn't tested 18/20 since they went EOL)
  • npm install on Node <22 shows engines warning

@WillieRuemmele WillieRuemmele requested a review from a team July 14, 2026 15:48
@WillieRuemmele WillieRuemmele force-pushed the wr/dropNode18And20Support branch from 6832ea0 to aea2bbf Compare July 14, 2026 16:07
@WillieRuemmele WillieRuemmele changed the title chore: drop Node 18/20 support, require >=22 @W-23388103@ fix: drop Node 18/20 support, require >=22 @W-23388103@ Jul 16, 2026
@WillieRuemmele

Copy link
Copy Markdown
Contributor Author

Closing — changing our approach to dropping Node 18/20 support (W-23388103). This declarative engines-only bump is being superseded; a new strategy will follow. Not merging this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

@salesforce/core declares Node >=18 but resolves @jsforce/jsforce-node >=3.10.17 which requires Node >=22 — runtime crash on Node 18/20

1 participant