NPM failure 'http fetch 404'


(ETP) #1

Iā€™m having a very weird issue with npm RemoteTarball operation where certain depencency packages are not getting fetched from my nexus server. The url formation in the getRemoteTarball operation is getting modified to an incorrect path and is causing failures.

Eg:
19461 silly mapToRegistry uri http://nexusurl.nexus:8081/nexus/content/repositories/npmjs-registry-org/@types%2Fcommander
19462 verbose addRemoteTarball http://nexusurl.nexus:8081/nexus/c/content/repositories/npmjs-registry-org/@types/commander/-/commander-2.12.2.tgz not in flight; adding

The artifact in nexus is present under
http://nexusurl.nexus:8081/nexus/content/repositories/npmjs-registry-org/commander

The .npmrc file correctly contains the npmjs-registry-org repository address as
http://nexusurl.nexus:8081/nexus/content/repositories/npmjs-registry-org/

Could someone help out on the reason why such a change is happening and how might it can be fixed?

node v6.10.1
npm v3.10.10


(system) #2

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.