-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SFDX 7.129.0 installed with npm does not work with node lts (16.13.0) #1300
Comments
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. |
I'm still using node 14 because jest tests are not working with the 16. Is there a reason for upgrading to node 16, besides the doc recommending to do so? According to this doc it's recommended to use sfdx with the "active lts" node version, which is the 16 at the moment. |
node14 is fine |
Also facing the issue when linking a plugin :( |
@DougMidgley how are u linking a plugin? And which plugin is it? |
@AllanOricil Its a custom plugin (not published as is private, so its not installing, but linking) below is the the sample. Note: the plugin works perfectly fine, just with this error which causes some concern to users.
Interestingly, this only happens when linking on the Azure DevOps Linux machine, when doing locally with Windows, no errors show |
we've changed the code for plugins:link You should see linked plugins compile themselves now, which I think was maybe at the root of some of this thread. As always, if you've got something still broken that's reproducible, please open a new issue. |
Summary
SFDX 7.129.0 installed with npm does not work with node lts (16.13.0)
Steps To Reproduce:
Expected result
display sfdx version
Actual result
fails
System Information
sfdx
sfdx version --verbose --json
- failssf
sf version
ANDsf plugins --core
Additional information
bang.
The text was updated successfully, but these errors were encountered: