Skip to content
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

SF_NPM_REGISTRY is not working #2517

Closed
gavignon opened this issue Oct 10, 2023 · 5 comments
Closed

SF_NPM_REGISTRY is not working #2517

gavignon opened this issue Oct 10, 2023 · 5 comments
Labels
bug Issue or pull request that identifies or fixes a bug validated Version information for this issue has been validated

Comments

@gavignon
Copy link

Summary

Environment variable SF_NPM_REGISTRY is not working

Steps To Reproduce

Install a sf plugin hosted on a private npm registry

  • SF_NPM_REGISTRY=URL sf plugins install {PLUGIN_NAME}

Expected result

SF Plugin is installed successfully

Actual result

Install fails because the private registry is not taken into account

Workaround

Use SFDX_NPM_REGISTRY variable instead

System Information

bash and zsh

{
  "cliVersion": "@salesforce/cli/2.11.8",
  "architecture": "darwin-x64",
  "nodeVersion": "node-v16.20.2",
  "osVersion": "Darwin 22.6.0",
  "shell": "zsh",
  "rootPath": "/Users/{USER}/.npm-global/lib/node_modules/@salesforce/cli",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 2.3.8 (core)",
    "@oclif/plugin-commands 2.2.26 (core)",
    "@oclif/plugin-help 5.2.19 (core)",
    "@oclif/plugin-not-found 2.4.1 (core)",
    "@oclif/plugin-plugins 3.8.2 (core)",
    "@oclif/plugin-search 0.0.22 (core)",
    "@oclif/plugin-update 3.2.3 (core)",
    "@oclif/plugin-version 1.3.10 (core)",
    "@oclif/plugin-warn-if-update-available 2.1.0 (core)",
    "@oclif/plugin-which 2.2.32 (core)",
    "@salesforce/cli 2.11.8 (core)",
    "apex 2.3.15 (core)",
    "auth 2.8.17 (core)",
    "data 2.5.12 (core)",
    "deploy-retrieve 1.18.3 (core)",
    "dev 1.1.10 (user)",
    "info 2.6.45 (core)",
    "limits 2.3.35 (core)",
    "login 1.2.31 (core)",
    "marketplace 0.2.2 (core)",
    "org 2.10.8 (core)",
    "packaging 1.20.0 (user)",
    "schema 2.3.28 (core)",
    "settings 1.4.30 (core)",
    "signups 1.4.22 (user)",
    "sobject 0.2.7 (core)",
    "source 2.10.36 (core)",
    "telemetry 2.3.4 (core)",
    "templates 55.5.13 (core)",
    "trust 2.6.15 (core)",
    "user 2.3.32 (core)"
  ]
}
@gavignon gavignon added the investigating We're actively investigating this issue label Oct 10, 2023
@github-actions
Copy link

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.

@github-actions github-actions bot added the validated Version information for this issue has been validated label Oct 10, 2023
@iowillhoit
Copy link
Contributor

Thanks @gavignon, It looks like it is setting the registry correctly but our code where we validate signatures only looks for SFDX_NPM_REGISTRY. We'll get a fix in!

@iowillhoit iowillhoit added bug Issue or pull request that identifies or fixes a bug and removed investigating We're actively investigating this issue labels Oct 11, 2023
@git2gus
Copy link

git2gus bot commented Oct 11, 2023

This issue has been linked to a new work item: W-14277809

@iowillhoit
Copy link
Contributor

This should be fixed in the nightly build. You can try it out at @salesforce/cli@nightly. It will be promoted to latest on October 25th

@jshackell-sfdc
Copy link
Collaborator

This issue is fixed in CLI version 2.14.6 (Oct 25, 2023).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue or pull request that identifies or fixes a bug validated Version information for this issue has been validated
Projects
None yet
Development

No branches or pull requests

3 participants