Retrieves packages not specified npm repository

[alexbel2404]

I'm opening this issue because:

• npm is crashing.
• npm is producing an incorrect install.
• npm is doing something I don't understand.
• Other (see below for feature requests):

What's going wrong?

I specify npm repository artifactory, but tries to download packages from registry.npmjs.org

How can the CLI team reproduce the problem?

npm install -g npmbox --registry=https://artifactory.local/api/npm/npm

npm sill mapToRegistry name assertion-error@https://registry.npmjs.org/assertion-error/-/assertion-error-1.0.2.tgz
npm sill mapToRegistry using default registry
npm sill mapToRegistry registry https://artifactory.local/api/npm/npm
npm sill mapToRegistry data Result {
npm sill mapToRegistry   raw: 'assertion-error@https://registry.npmjs.org/assertion-error/-/assertion-error-1.0.2.tgz',
npm sill mapToRegistry   scope: null,
npm sill mapToRegistry   escapedName: 'assertion-error',
npm sill mapToRegistry   name: 'assertion-error',
npm sill mapToRegistry   rawSpec: 'https://registry.npmjs.org/assertion-error/-/assertion-error-1.0.2.tgz',
npm sill mapToRegistry   spec: 'https://registry.npmjs.org/assertion-error/-/assertion-error-1.0.2.tgz',
npm sill mapToRegistry   type: 'remote' }
npm sill mapToRegistry uri https://registry.npmjs.org/assertion-error/-/assertion-error-1.0.2.tgz
npm verb scopeAuth alwaysAuth set for https://artifactory.local/api/npm/npm
npm verb addRemoteTarball https://registry.npmjs.org/assertion-error/-/assertion-error-1.0.2.tgz not in flight; adding
npm verb addRemoteTarball [ 'https://registry.npmjs.org/assertion-error/-/assertion-error-1.0.2.tgz',
npm verb addRemoteTarball   null ]

supporting information:

• npm -v prints:
  v6.8.0
• node -v prints:
  3.10.8
• npm config get registry prints:
  https://artifactory.local/api/npm/npm
• Windows, OS X/macOS, or Linux?:
  Linux
• Network issues:
  • Geographic location where npm was run:
  • I use a proxy to connect to the npm registry.
  • I use a proxy to connect to the web.
  • I use a proxy when downloading Git repos.
  • I access the npm registry via a VPN
  • I don't use a proxy, but have limited or unreliable internet access.
• Container:
  • I develop using Vagrant on Windows.
  • I develop using Vagrant on OS X or Linux.
  • I develop / deploy using Docker.
  • I deploy to a PaaS (Triton, Heroku).

[legodude17]

That isn't really npm's fault, it was just using the Result it got from https://artifactory.local/api/npm/npm. That registry sent the spec as something on https://registry.npmjs.org.

[npm-robot]

We're closing this support issue as it has gone three days without activity. The npm CLI team itself does not provide support via this issue tracker, but we are happy when users help each other here. In our experience once a support issue goes dormant it's unlikely to get further activity. If you're still having problems, you may be better served by joining package.community and asking your question there.

For more information about our new issue aging policies and why we've instituted them please see our blog post.