Nodist can't find npm version 7.14.0

Question

Nodist can't find npm version 7.14.0

premedios opened this issue 3 years ago · comments

When I run nodist npm 7.14.0, it returns with Unhandled rejection {"message":"Bad credentials","documentation_url":"https://docs.github.com/rest"}.

If I I run npm install -g npm@7.14.0, it complains about npm.cmd and suggests that I run the command with --force.. If I run the command with --force it works.

Martijn Dormans · Answer 1 · Fri May 28 2021 20:15:11 GMT+0800 (China Standard Time)

Yis i got the exact same error. Even when I try to install npm version 6.14.13 with the command: nodist npm 6.14.13. So I think there is something wrong with nodist and npm.

pocfusion1 · Answer 2 · Sun May 30 2021 18:54:50 GMT+0800 (China Standard Time)

Yeah i too facing the same issue when i try this command nodist npm 6.14.12
getting this below error

npm 6.14.12
{"message":"Bad credentials","documentation_url":"https://docs.github.com/rest"}.
Sorry.

Martijn Dormans · Answer 3 · Mon May 31 2021 01:03:17 GMT+0800 (China Standard Time)

You can do a quick fix by installing npm without using nodist. So by using the following command: npm i -g npm@latest.

Bryan Tong · Answer 4 · Mon May 31 2021 01:13:26 GMT+0800 (China Standard Time)

Hello, I will take a look into fixing this tomorrow. Sorry for the trouble. Thank you

JellevanHaaften · Answer 5 · Tue Jun 01 2021 05:12:46 GMT+0800 (China Standard Time)

Having the same issue :(

Gama · Answer 6 · Thu Jun 03 2021 00:22:06 GMT+0800 (China Standard Time)

nodist npm match worked.

Martijn Dormans · Answer 7 · Thu Jun 03 2021 01:50:21 GMT+0800 (China Standard Time)

nodist npm match worked.

And what npm version will it install if you use it?

Gama · Answer 8 · Fri Jun 04 2021 18:50:34 GMT+0800 (China Standard Time)

nodist npm match worked.

And what npm version will it install if you use it?

npm corresponding to the installed Node will be installed.
see here: https://nodejs.org/ja/download/releases/

GAMA@GAMANS-AM MINGW64 /d
$ nodist npm
  6.9.0
  6.14.11
> 6.14.13  (global: match)

GAMA@GAMANS-AM MINGW64 /d/workspace
$ node -v
v14.15.0

GAMA@GAMANS-AM MINGW64 /d/workspace
$ nodist npm match
npm match
https://codeload.github.com/npm/cli/tar.gz/v6.14.8 [============== ] 4996/5507 KiB 90% 0.0s

GAMA@GAMANS-AM MINGW64 /d/workspace
$ nodist npm
  6.9.0
> 6.14.8  (global: match)
  6.14.11
  6.14.13

Bryan Tong · Answer 9 · Sat Jun 05 2021 08:53:48 GMT+0800 (China Standard Time)

Hello,

I spent some time on this issue today and issued a patch here: #234

For anyone with an existing version the issue can be easily avoided by replacing the nodist/lib/github.js file. I will attach that file to this comment.

Additionally, I will propagate a new version being that the older key is now invalidated.

#232 is duplicate of this.

Bryan Tong · Answer 10 · Fri Jun 11 2021 03:43:05 GMT+0800 (China Standard Time)

Merged the patch today. I will work up a new version.

Craig P Hicks · Answer 11 · Mon Oct 11 2021 04:47:36 GMT+0800 (China Standard Time)

Hello,
...
For anyone with an existing version the issue can be easily avoided by replacing the nodist/lib/github.js file. I will attach that file to this comment.

Where is the attached file you mention? I am running 9.1 - should that already have the patch?

Cagdas U. · Answer 12 · Thu Nov 04 2021 23:47:09 GMT+0800 (China Standard Time)

Here is the file he mentions: https://github.com/nullivex/nodist/blob/master/lib/github.js Replace Nodist/lib/github.js with this file

Sebastian Große · Answer 13 · Sat Dec 09 2023 18:39:14 GMT+0800 (China Standard Time)

Has been fixed in v.10.3