"SFDX: Deploy This Source to Org" command resulting in "Object.groupBy is not a function" output

[wdsking]

Summary

Hello, on 21.11.2025 ~17:00 GMT+1 I encountered an issue during metadata deployment using the "SFDX: Deploy This Source to Org" command resulting in an error and following output:

I'm performing the deployment as usual by right clicking current file and selecting the command option, it neither works from the file explorer nor the command palette. It seems like metadata type doesn't matter, it occured on Apex class however I reproduced it on Layouts as well.

It's worth mentioning that earlier that day I was able to use the command successfully and didn't receive any errors.

It may be related to some Windows/WSL updates, I asked my friend who use WSL on one device and macOS on another and he said that the problem also started to appear on his WSL, but not on the macOS. My co-workers who don't use WSL at all haven't encountered such issues yet.

A workaround I found for now is to perform a deployment using SF CLI directly.

Steps To Reproduce:

1. Right click on .cls file
2. Select the "SFDX: Deploy This Source to Org" command
3. Wait for the command to fail and observe the output

Expected result

Metadata is deployed to active Salesforce org successfully.

Actual result

An error occurs and output states:

=== Deployed Source
No results found

Object.groupBy is not a function

Additional information

I've tried upgrading Node version from 18 to 22, reinstalling the CLI, reinstalling the Salesforce Extension Pack. I'm not sure if it's related to the Salesforce Extension Pack version because I've tried to downgrade it and the same issue occured.

Cursor IDE Version:

Salesforce Extension Version in VS Code: 65.5.0

Salesforce CLI Version: @salesforce/cli/2.113.6 wsl-x64 node-v22.21.1

OS and version: WSL2 Ubuntu (Linux 6.6.87.2-microsoft-standard-WSL2)

VS Code version: 1.105.1

Most recent version of the extensions where this was working: 65.4.0

[svc-idee-bot]

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.

[svc-idee-bot]

Hello @wdsking 👋 It looks like you didn't provide all the required basic info in your issue.

If you haven't already, please provide the following info:
Salesforce Extension Version in VS Code:
Salesforce CLI Version:
OS and version:
VS Code version:
Most recent version of the extensions where this was working:

Here's an example of a set of required info that will pass the validation:
Salesforce Extension Version in VS Code: 60.13.0
Salesforce CLI Version: @salesforce/cli/2.42.6 darwin-arm64 node-v18.18.2
OS and version: MacOS Sonoma 14.5
VS Code version: 1.89.1
Most recent version of the extensions where this was working: 60.11.0

A few more things to check:

• Make sure you've provided detailed steps to reproduce your issue, as well as all error messages that you see.
  • A repository that clearly demonstrates the bug is ideal.
  • Error messages can be found in the Problems Tab, Output Tab, and from running Developer: Toggle Developer Tools in the command palette.
• Make sure you've installed the latest version of the Salesforce Extension Pack for VSCode. (docs)
• Search GitHub for existing related issues.

Thank you!

[mshanemc]

aww, I checked the docs here https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/groupBy to make sure that was safe and we run e2e tests on windows, too.

all of your info points toward node22 VS Code version: 1.105.1
https://github.com/ewanharris/vscode-versions

out of curiosity, is it broken for both Cursor and VSCode on current versions on WSL? If it's just Cursor, it's might be something they've built wrong.

[wdsking]

aww, I checked the docs here https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/groupBy to make sure that was safe and we run e2e tests on windows, too.

all of your info points toward node22 VS Code version: 1.105.1 https://github.com/ewanharris/vscode-versions

out of curiosity, is it broken for both Cursor and VSCode on current versions on WSL? If it's just Cursor, it's might be something they've built wrong.

Thanks for the reply and suggestion. I checked the case on VS Code and it looks like the issue doesn't occur here. I tested it on the 1.105.1 (same as in Cursor) and 1.106.2 (latest one) version, both running the same Salesforce Extension Pack, SF CLI and connected to the same WSL and repository. It could be indeed related to the specific Cursor build, I'll check if it's possible to downgrade it and will let you know.

[wdsking]

What I tried so far (in addition to things I mentioned in my issue description) that didn't fix the problem:

• Downgraded Cursor version to the 1.7 and 2.0 version.
• Removed Cursor directory from "C:\Users\MyUser\AppData\Roaming\Cursor"
• Updated WSL to pre-release 2.6.2 version

[2904nando]

I'm also getting this error... In VSCode it appear to work, but on Cursor, I'm not having any luck.
Tried to completely remove SF cli from my system, reinstall extensions, clear npm cache before reinstalling sf cli, clear Cursor cache, but nothing works.

I'm at Cursor's latest version, SF CLI latest version and it just gives me the same result as OP's.

I'll try downgrading Cursor in the following hours to validate if some version got something wrong.

PS: Also other commands seem to also fail, for example, the diff command:

Or the retrieve command:

This class is already on the org, always worked as expected and works on VSCode.

[2904nando]

Running the command directly works as expected, so not a problem with the SF CLI
Example:

sf project deploy start --source-dir force-app/main/default/classes/TestClass.cls

works as expected

[mshanemc]

@2904nando it's definitely a change we made (I remember enabling it), so downgrading cursor won't help.

VSCode has been on Node22+ since May (1.101) https://github.com/ewanharris/vscode-versions so that 105 you have should be fine. We don't run automated tests using cursor (just vscode) so if they've got something screwy in the their build (ex: somehow being on an old node version) that's not something we'd catch.

Can you open a Cursor issue? I'd be curious if any other extension that works for vscode and fails in recent Cursor due to missing language features.

[wdsking]

@mshanemc @2904nando I've created a Cursor issue which you can follow under this link https://forum.cursor.com/t/possible-node22-language-features-missing-salesforce-extension-pack-impacted/145566.