Issue verification check :
[] Is current package working in Salesforce CLI within windows?
I have installed the latest version of SFDX from below URL:
https://developer.salesforce.com/tools/sfdxcli
But it shows latest node version as v12.18.3:
sfdx-cli/7.84.2-a2868a68d5 win32-x64 node-v12.18.3
I separately installed nodeJS latest version globally. Then also Salesforce CLI refers the node-v12.18.3, which is available under the Salesforce CLI folder.
Any workaround or suggestion will be helpful to us. So, we can use the addon in windows Salesforce CLI.
_(Write your answer here.)_
_(Write your answer here.)_
_(Write your answer here.)_
_(Write your answer here.)_
_(Write your answer here.)_
Operating System: …
Yarn version: …
Node version: …
sgd version: …
SDK Version: …
_(Write your answer here.)_
Hi @ashishshukla38 !
If I understand well, executin the CLI sfdx on windows seems to use the inner sfdx node installation (v12) instead of the node version installed in the local machine even if there is a local node version installed on the machine right ?
If then, it looks like an issue with the CLI itself...
Could you fill the PR with Execution context information please ?
This looks like a duplicate of https://github.com/scolladon/sfdx-git-delta/issues/85
Node v14.6.0 or above is required for the SGD plugin.
The current Salesforce CLI installer comes with node v12, which cannot be used with SGD. So, until the Salesforce CLI is upgraded with a more recent version of node, you will have to install the Salesforce CLI via npm.
This means that you should be able to solve your issue by:
Thanks a lot @scolladon and @mehdisfdc for your quick response. We will try the following steps mentioned by @mehdisfdc .
Thanks for the tip @mehdisfdc ! I was having the same issue. Completely uninstalling the Windows version and the npm version, then reinstalling only via npm resovled the issue for me.
Most helpful comment
Thanks for the tip @mehdisfdc ! I was having the same issue. Completely uninstalling the Windows version and the npm version, then reinstalling only via npm resovled the issue for me.