cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CB-12774) cordova plugin add doesn't support scoped packages from private registries
Date Thu, 06 Sep 2018 18:28:00 GMT


ASF GitHub Bot commented on CB-12774:

raphinesse commented on issue #602: CB-12774 : Don't munge scoped plugin IDs anymore. Comment
   @oliversalzburg Great to hear! OP hasn't reacted to previous mentions, so I'd suggest you
open a PR with the rebased changes that references this one. Then we can have another look
at it.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> cordova plugin add doesn't support scoped packages from private registries
> --------------------------------------------------------------------------
>                 Key: CB-12774
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: cordova-lib
>    Affects Versions: 1.1.0
>            Reporter: Enrico Mazzucchelli
>            Assignee: Raphael
>            Priority: Major
>              Labels: cordova-8.0.0
>             Fix For: 1.1.1
> 1) setup a private repo (for example sinopia with docker:
> 2) add scope in your npm config:  npm config set @myco:registry
> 3) create you plugin. In package.json set name: @myco/; in plugin.xml
set plugin id: @myco/
> 3) publish plugin in your private repo:
>     - npm set registry
>     - npm publish
>    -  npm set registry
> 4) in your cordova project dir, exec:
>     cordova plugin add @myco/
>   cordova plugin are installed 
>   cordova installation failed:
>   Error: Failed to fetch plugin via registry.
>   Probably this is either a connection problem, or plugin spec is incorrect.
>   Check your connection and plugin name/version/URL.
>   Error: npm: Command failed with exit code 1 Error output:
>   npm ERR! code E404
>   npm ERR! 404 Registry returned 404 for GET on
>   npm ERR! 404 
>   npm ERR! 404  '' is not in the npm registry.
>   npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
>   npm ERR! 404 
>   npm ERR! 404 Note that you can also install from a
>   npm ERR! 404 tarball, folder, http url, or git url.
> However node module are correctly installed (verified with npm ls) and fetch.json have
a new entry with key

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message