Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

400 Bad Request: npm@latest #19682

Closed
2 of 5 tasks
ghost opened this issue Jan 24, 2018 · 2 comments
Closed
2 of 5 tasks

400 Bad Request: npm@latest #19682

ghost opened this issue Jan 24, 2018 · 2 comments
Labels

Comments

@ghost
Copy link

ghost commented Jan 24, 2018

I'm opening this issue because:

  • npm is producing an incorrect install.
  • npm is doing something I don't understand.

What's going wrong?

C:\Program Files\IBM\IIB\10.0.0.4>node -v
v8.9.4

C:\Program Files\IBM\IIB\10.0.0.4>npm -v
5.6.0

C:\Program Files\IBM\IIB\10.0.0.4>npm install -g apiconnect
npm ERR! code E400
npm ERR! 400 Bad Request: apiconnect@latest

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\sadea\AppData\Roaming\npm-cache_logs\2018-01-24T05_21_22_
430Z-debug.log

How can the CLI team reproduce the problem?

Running the above commands.
https://gist.github.com/akiransa/aa46b539729d82f768b219f510bbb03a

supporting information:

  • npm -v prints: 5.6.0
  • node -v prints:v8.9.4
  • npm config get registry prints: https://registry.npmjs.org/
  • Windows, OS X/macOS, or Linux?: Windows
  • Network issues:
    • Geographic location where npm was run: India
    • 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.
@ghost
Copy link
Author

ghost commented Jan 24, 2018

@ghost ghost closed this as completed Jan 24, 2018
@ghost
Copy link
Author

ghost commented Jan 24, 2018

It looks like it would work with older version of npm v3.x.x as per the documentation. Hence closing this as this is not a valid issue.

@kenany kenany added the support label Jan 24, 2018
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant