-
Notifications
You must be signed in to change notification settings - Fork 88
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
zowe plugins list
registry qualification
#63
Comments
From @AHumanFromCA on May 17, 2018 14:17 This requires an enhancement to imperative. |
From @AHumanFromCA on August 20, 2018 14:4 Perhaps a quick way to address this is when listing or installing plugins we could output every scoped registry we find. Then we could change the --registry flag to be --non-scoped-registry or keep the flag the same and change the doc so that people understand what is happening. Otherwise you would say that the registry would be bintray but that is also a lie since only the scoped packages are downloaded from there, everything else is pulled from the npm registry. |
Our CLI component is not hosted on a registry at all yet is shown as the above example on a zowe plugins list - incorrectly in my view. I tried adding private: true to package.js but it made no difference. |
From an internal conversation:
Edit: This metadata appears to no longer be generated by npm@8 😢 |
bright plugins list
registry qualification zowe plugins list
registry qualification
As recently discussed, it may be better to not display the registry at all. |
--no-location as a new flag |
From @dkelosky on May 17, 2018 14:15
If a plugin is installed via a scoped registry, the scoped registry is not displayed on the
zowe plugins list
command.For example, if scoped package
xyz
where installed from a registry qualified by the scopedzowe
the displayed registry could be misleading.In other words if
@zowe/xyz
were installed from a registry hosted on JFrog, it could be displayed as though it came fromnpmjs
:Copied from original issue: gizafoundation/brightside#77
The text was updated successfully, but these errors were encountered: