NPM adduser - Not Found

[beda]

Hi,
I'm running latest LTS node.js 6.11.4 and ProGet 4.8.6 on Windows Server 2016 x64. If I run npm adduser command it failes with 404 NotFound error. Here is npm log:

2 info using npm@5.5.1
3 info using node@v6.11.4
4 verbose config Skipping project config: C:\Users\<user>/.npmrc. (matches userconfig)
5 verbose stack Error: Not Found
5 verbose stack     at fetch.defaults.then.then.result (C:\Users\<user>\AppData\Roaming\npm\node_modules\npm\node_modules\npm-profile\index.js:203:19)
5 verbose stack     at process._tickCallback (internal/process/next_tick.js:109:7)

In ProGet IIS log there is PUT request:
PUT /npm/-/user/org.couchdb.user:devpub - 80 - <IP> make-fetch-happen/2.5.0+(+https://npm.im/make-fetch-happen) - 404 0 0 31

It used to works on older node.js 4.5.0. There was this PUT request to ProGet IIS:
PUT /npm/dev_npm/-/user/org.couchdb.user:devpub - 80 - <IP> npm/3.10.7+node/v4.5.0+win32+x64 adduser 201 0 64 203

So in new node.js version there isn't ProGet npm feed name in URL (dev_npm) what cause 404.

Is it problem in node.js or it should be fixed in ProGet?

Thanks,
beda

Product: ProGet
Version: 4.8.6

[beda]

Now I test node.js 6.11.3 and it works. So only latest 6.11.4 is broken. In 6.11.3 PUT request still contains npm feed name:

PUT /npm/dev_npm/-/user/org.couchdb.user:devpub - 80 - <IP> npm/3.10.10+node/v6.11.3+win32+x64 adduser 201 0 0 78

[ben]

Hello beda,

It appears that npm 5.5.1 (the node:6.11.4 Docker image has npm 3.10.10 by default) strips anything after the last slash in the registry URL. To work around this, add a slash at the end, so --registry=https://proget/npm/my-feed-name becomes --registry=https://proget/npm/my-feed-name/

[beda]

Hello Ben,

thanks for help. I can confirm that node.js v 6.11.4 with slash at the end of URL works ;)