Command failed: sf org login sfdx-url --sfdx-url-file files/authFile.json --alias MyDefaultOrg --json , Error/Warning: Detected unsettled top-level await at node_modules/@salesforce/cli/bin/run.js:15 await cli.run();

[PankajamM]

Command failed: sf org login sfdx-url --sfdx-url-file files/authFile.json --alias MyDefaultOrg --json

Error received :
Warning: Detected unsettled top-level await at file://node_modules/@salesforce/cli/bin/run.js:15 await cli.run();

I am using Salesforce CLI version 2.139.6 installed via npm (@salesforce/cli) and running the command in CI with:

Node.js: v24 (and also tested with v22)
OS: GitHub Actions Ubuntu runner

The issue is reproducible consistently with:

sf org login sfdx-url --sfdx-url-file --alias --json

Error observed:

Warning: Detected unsettled top-level await at @salesforce/cli/bin/run.js

The same setup works correctly with Node.js v20, but fails on Node 22 and 24 with the above runtime warning and CLI failure during bootstrap.

Please confirm if Salesforce CLI 2.139.x supports Node 24 in npm-based installations, or if there is a known compatibility issue with the CLI bootstrap process under Node 24.

[github-actions]

Hello @PankajamM 👋 It looks like you didn't include the full Salesforce CLI version information in your issue.
Please provide the output of version --verbose --json for the CLI you're using (sf or sfdx).

A few more things to check:

• Make sure you've provided detailed steps to reproduce your issue.
  • A repository that clearly demonstrates the bug is ideal.
• Make sure you've installed the latest version of Salesforce CLI. (docs)
  • Better yet, try the rc or nightly versions. (docs)
• Try running the doctor command to diagnose common issues.
• Search GitHub for existing related issues.

Thank you!

[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.

[PankajamM]

Thanks for the response.

I am using Salesforce CLI version 2.139.6 installed via npm (@salesforce/cli) and running the command in CI with:

Node.js: v24 (and also tested with v22)
OS: GitHub Actions Ubuntu runner

The issue is reproducible consistently with:

sf org login sfdx-url --sfdx-url-file --alias --json

Error observed:

Warning: Detected unsettled top-level await at @salesforce/cli/bin/run.js

The same setup works correctly with Node.js v20, but fails on Node 22 and 24 with the above runtime warning and CLI failure during bootstrap.

Please confirm if Salesforce CLI 2.139.x supports Node 24 in npm-based installations, or if there is a known compatibility issue with the CLI bootstrap process under Node 24.

[sauloefo]

Hi folks, I hit this same issue and asked Claude to help me with the root-cause analysis. I hope it helps:

---

Root cause: the bundled node-fetch@2.7.0 (via @jsforce/jsforce-node) fails to
decompress gzip responses on Node ≥22, and jsforce-node swallows the resulting stream
error, so the request promise never settles — which is what surfaces as the "unsettled
top-level await" / exit 13.

Repro matrix (CLI 2.139.6, @jsforce/jsforce-node 3.10.15 → node-fetch 2.7.0, linux):
Node 18.20.8 ✅ · 20.20.2 ✅ · 22.23.0 ❌ · 24.17.0 ❌

It is NOT specific to org login sfdx-url — it hits any command that makes an API call
(login, org display, deploy, query, bulk; org list with no saved org only "works"
because it makes no network call).

Mechanism (traced with async_hooks + node-fetch in isolation):

1. The request itself is fine — the OAuth/token call returns HTTP 200. The failure is in
   reading the response body.
2. node-fetch sends Accept-Encoding: gzip; Salesforce responds Content-Encoding: gzip.
   On Node ≥22, node-fetch 2.7.0's gunzip stream throws FetchError: ... Premature close.
   Node's built-in fetch (undici) and raw https read the same response fine, so this is a
   node-fetch v2 incompatibility with Node ≥22's stricter stream-end handling, not a Node
   core bug.
3. In @jsforce/jsforce-node/lib/request.js (startFetchRequest) the body is consumed via
   res.body.pipe(output) (→ request-helper.js → util/stream.js readAll). .pipe()
   does not forward the source's error, and there's no error handler on res.body, so
   the "Premature close" is swallowed. readAll resolves on the downstream 'finish',
   which never fires; the socket has already closed so no libuv handle remains, the loop
   drains, and await cli.run() is left unsettled → exit 13.

Minimal proof (Node 24):

const fetch = require('node-fetch'); // the 2.7.0 bundled by the CLI
const res = await fetch(url, { method:'POST', body, headers });   // 200, content-encoding: gzip
await res.text();                    // ❌ "Premature close" on Node 22/24, ✅ on 18/20
// res with { compress:false }       // ✅ on all versions (no gzip requested)

[trysmr]

Hi,

I’m seeing what looks like the same issue, but with a narrower reproduction around the June 18, 2026 Node.js security releases.

I tested the same Salesforce CLI version with the immediately preceding Node.js versions and the June 18 security release versions.

Environment:

• @salesforce/cli 2.139.6
• darwin-arm64
• npm-installed CLI under mise-managed Node.js

Command:

sf doctor

Working:

• Node 22.22.3
• Node 24.16.0
• Node 26.3.0

Failing:

• Node 22.23.0
• Node 24.17.0
• Node 26.3.1

Observed failure:

The command does not complete. It stops after:

fail - [@salesforce/plugin-auth] CLI supports v2 crypto

Then Node.js prints:

Warning: Detected unsettled top-level await at .../@salesforce/cli/bin/run.js:15
await cli.run();

In the working versions, sf doctor completes and writes the diagnosis JSON file.

Since all failing versions are Node.js June 18, 2026 security releases, while the immediately preceding versions work, this appears to be triggered by the June 18 Node.js security updates rather than by a specific Node.js major version.

Hope this helps narrow it down.

[nwcm]

Also seeing this issue. With either

@salesforce/cli/2.130.9 win32-x64 node-v22.23.0
@salesforce/cli/2.138.6 win32-x64 node-v24.17.0