Possible Node22 language features missing, Salesforce Extension Pack impacted

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hello, I’m a Salesforce Developer who uses Cursor IDE with official Salesforce Extension Pack installed from the Marketplace. I’ve been using the IDE for months and haven’t encountered any problems until 21.11.2025 ~17:00 GMT+1 when I’ve started experiencing issues with using Commands (from context menus, file explorer, command palette). At first I decided to create an issue on the extension’s GitHub repository and received an information that now they’re using node 22’s native methods, before the implementation they checked the compatibility with VSCode and every tests passed. They advised me to check if the problem occurs on VSCode and unfortunately it doesn’t. I checked the same VS Code version as stated in Cursor’s Help → About which is 1.105.1.

I’ve tried reinstalling the CLI, reinstalling the Salesforce Extension Pack, upgrading WSL version, downgraded Cursor version to the 1.7 and 2.0 version, removed Cursor directory from “C:\Users\MyUser\AppData\Roaming\Cursor”.

For now a workaround I found is deploying the metadata directly with SF CLI instead of a command, however it’s a less convenient way to perform such operations.

It’s worth mentioning that VSCode has been on Node22+ since May (1.101) so the 1.105 version should be fine. Is there anything on Cursor side that could make these features missing?

Steps to Reproduce

  • Use latest version of Cursor
  • Have the Salesforce Extension Pack installed
  • Connect to any org
  • Try to deploy any metadata using the “SFDX: Deploy This Source to Org” command
  • Observe that the command fails

Expected Behavior

Command doesn’t fail and metadata is correctly deployed to active org.

Screenshots / Screen Recordings

Zrzut ekranu 2025-12-08 162018.png
Zrzut ekranu 2025-12-08 162018.png796×213 8.1 KB

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.50 (system setup)
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Date: 2025-12-06T23:39:52.834Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

4

I’m having this issue as well. On Win + WSL.

6

Same issue here, can’t use Cursor with the Salesforce Extension, only directly calling the CLI commands from the terminal =/

Tried reinstalling everything, but nothing seems to work. Also on Windows 11 + WSL2. Maybe there’s a problem with the Cursor-server on WSL? Couldn’t install a specific version of that to test it though..

8

While Cursor’s “About” dialog shows VSCode Version: 1.105.1, that currently refers to API compatibility, not the actual VSCode codebase.

We periodically merge upstream changes from VSCode, and the last merge was from version 1.99.3. So updates made after that aren’t in Cursor yet.

This should be resolved when the next VSCode merge happens, but I don’t have an ETA for that!

That said, the more issues like this that pop up, the easier a case it is to make that we should prioritize this. So thanks for reporting :folded_hands:

9

Any updates on this one? ETA? Our Salesforce dev team is back on VSCode since the issue is pretty disruptive. We can no longuer push/retrieve metadata from our sandbox environnements.

11

Thank you for raising this issue; we are working on a fix for this to support the NodeJS 22 API’s in the extension host.

Edit: This fix will be available in the Cursor 2.4 release, which should be coming out this month.

12

For those wondering, this is now resolved on my end in today’s release (2.4.7)!!! All functions are back to normal (deployment, diff views, retrievals, etc)

Thanks Cursor team!!

13

That’s great to hear! Is there any way to enforce an update? I have the 2.3.41 version and using built in “Check for updates” option says there are no new updates available.

15

An official announcement is coming soon, and updates will roll out gradually. :slight_smile: You can also switch to Early Access / Nightly release tracks (Cursor Settings > General > Beta) if you want to speed things up.

16

Thanks for mentioning the possibility to switch to Early Access. I did it and now I’m on 2.4.7 where the issue is gone!