[ 
https://issues.apache.org/jira/browse/CB-9093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Raphael resolved CB-9093.
-------------------------
    Resolution: Fixed

This should be resolved in cordova@latest or cordova@nightly. If the issue 
persists, please let us know.

> Cordova doesn't work with private npm registry
> ----------------------------------------------
>
>                 Key: CB-9093
>                 URL: https://issues.apache.org/jira/browse/CB-9093
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: cordova-lib
>    Affects Versions: 5.0.0
>            Reporter: Patrick Wolf
>            Priority: Major
>
> We have a private npm registry using Sinopia, which requires authentication.
> When I try to use "cordova plugin add foobar", I get an error
> Fetching plugin "foobar" via npm
> Fetching from npm failed: Cannot insert data into the registry without auth
> Error: Cannot insert data into the registry without auth
>     at RegClient.regRequest [as request] 
> (/home/patrick/.nvm/versions/node/v0.12.4/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:96:15)
>     at RegClient.get_ 
> (/home/patrick/.nvm/versions/node/v0.12.4/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/npm/node_modules/npm-registry-client/lib/get.js:116:8)
>     at RegClient.<anonymous> 
> (/home/patrick/.nvm/versions/node/v0.12.4/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/npm/node_modules/npm-registry-client/lib/get.js:43:15)
>     at FSReqWrap.oncomplete (fs.js:95:15)
> I suspect this might be a problem with the older version of npm, 1.3.4, 
> included with Cordova.  It seems like npm-registry-client/lib/request.js 
> isn't properly handling the auth settings in npmrc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to