Npm login issues

[Kasper Bøgebjerg Pedersen]

Hi Proget,

We're experiencing problems with npm login after upgrading to npm 5.5.0.

npm adduser gives a 404 Not Found with npm 5.5.0 and works with npm 5.4.2

Product: ProGet
Version: 4.8.4

[Kasper Bøgebjerg Pedersen]

I tried to upload an image showing the error, but it didn't seem to work. Here it is in text instead:

$ npm --version
5.5.0

$ npm adduser --registry=http://myserver--scope=@myscope --allways-auth
Username: kasper
Password:
Email: (this IS public) kasper@mydomain.com
npm ERR! code E404
npm ERR! 404 Not Found

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\kasper.CONFIGIT\AppData\Roaming\npm-cache\_logs\2017-11-15T06_02_50_396Z-debug.log

$ npm install --global npm@5.4.2
C:\Users\kasper.CONFIGIT\AppData\Roaming\npm\npm -> C:\Users\kasper.CONFIGIT\AppData\Roaming\npm\node_mo
dules\npm\bin\npm-cli.js
C:\Users\kasper.CONFIGIT\AppData\Roaming\npm\npx -> C:\Users\kasper.CONFIGIT\AppData\Roaming\npm\node_mo
dules\npm\bin\npx-cli.js
+ npm@5.4.2
added 2 packages, removed 52 packages and updated 29 packages in 17.05s

$ npm adduser --registry=http://myserver --scope=@myscope --allways-auth
Username: kasper
Password:
Email: (this IS public) kasper@mydomain.com
Logged in as kasper to scope @mydomain on http://myserver.

[ben]

Hello Kasper,

I can't find where I solved this before, but I think the solution was to add a trailing slash to the registry URL. That is, if your registry is at http://example.com/npm/example-npm-feed, you would need to specify the parameter for npm 5.5 as --registry=http://example.com/npm/example-npm-feed/

[Kasper Bøgebjerg Pedersen]

Thanks Ben that did the trick :-)