sfdx plugins:install @<org_scope>/<plugin_name> error: pluginName cannot be nll about sfdx-plugin-generate HOT 4 CLOSED

@squibobblepants Thanks for opening the issue. We are aware of this problem and I'm actually working on a fix for this as I type this. As you surmised, the digital signature check doesn't support scopes in the npm names.

from sfdx-plugin-generate.

This should be fixed now with the latest version of the cli sfdx-cli/6.13.0.

from sfdx-plugin-generate.

I'm afraid this doesn't work for me on version 6.13.0

$ sfdx plugins:install @desynit/dsy-sfdx-plugins
Installing plugin @desynit/dsy-sfdx-plugins...
Installing plugin @desynit/dsy-sfdx-plugins... Checking for digital signature.
Finished digital signature check. Skipping... !
 !    The url request returned 404 - https://registry.npmjs.org/@desynit/dsy-sfdx-plugins

I think the problem is that the forward slash needs to be html encoded like so:
https://registry.npmjs.org/@desynit%2fdsy-sfdx-plugins

But If I do that in the cli like so

$ sfdx plugins:install @desynit%2fdsy-sfdx-plugins
Installing plugin @desynit%2fdsy-sfdx-plugins...
Installing plugin @desynit%2fdsy-sfdx-plugins... Checking for digital signature.
 !    The npm name is missing or invalid.

It doesn't work. Am I missing something maybe?

Version info:

$ sfdx --version
sfdx-cli/6.13.0-3bc8bd73d8 (windows-x64) node-v8.9.4

from sfdx-plugin-generate.

We actually ran into that problem on one of our local npm servers but not the other OR with registry.npmjs.org. Now when I do it against npmjs, I get the same error... @tnoonan-salesforce I think we will have to add in the encoding after all.

from sfdx-plugin-generate.