So basically I am trying to download packages from https://registry.npmjs.org/ using npm install, but I am under a proxy.
I have set-up a remote repository that will hit (above link) and cache using artifactory, so that I can pull locally, but it does not seem to work.
Followed these directions: http://www.jfrog.com/confluence/display/RTF/Npm+Repositories
Anyone else experience difficulties with proxy? I have seen many posts on changing config settings, but this is not what I need, I have to follow artifactory to get what I need, and I have changed my config settings accordingly to how artifactory advises, ie npm config set registry
Thanks!
Try removing proxy and https_proxy from .npmrc and configure the Proxy settings in Artifactory
Along with above answer,Please ensure that following option has been added to properties file.
$ARTIFACTORY_HOME/tomcat/conf/catalina.properties file (for Artifactory 4.x) or %ARTIFACTORY_HOME%\etc\artifactory.system.properties for Artifactory 3.x.
org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true
The error message indicated that npm tried looking for a package named 'artifactory' instead of 'bower' :
This can happen due to various misconfiguration:
npm config set registry http://myserver:8081/artifactory/api/npm/npmjs-registry/artifactory
Both cases will cause Artifactory to send requests to the public registry with the following URL: https://registry.npmjs.org/artifactory/bower instead of https://registry.npmjs.org/bower
In order to make sure your setup is correct, try the following:
Verify the registry URL stored in the
.npmrc
configuration file. For example, you can send a request for getting the 'bower' package info:curl -vv http://myserver:8081/artifactory/api/npm/npm-repo-name/bower
If npm install still fails, look at the npm-debug.log and the Artifactory log files for more info