npm publish 404 Not Found - PUT

[1000i100]

The nearest issue is #1626 but it's about using npm to get package, and it look solved for most user.
Here it's about npm publishing package in CI, and it's not solved for now.

Current Behavior:

https://framagit.org/1000i100/g1lien/-/jobs/1072053

$ npm publish
[...]
npm ERR! code E404
npm ERR! 404 Not Found - PUT https://registry.npmjs.org/g1link - Not found
npm ERR! 404 
npm ERR! 404  'g1link@0.1.1' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
[...]

Expected Behavior:

Successful publish of my package from docker in gitlab-CI with npm_token authentication.
(it works yesterday on my laptop with npm login, but not with npm_token in CI).

Steps To Reproduce:

ex. steps to reproduce the behavior:

1. Fork this : https://framagit.org/1000i100/g1lien
2. change the package name and add your npm token
3. push it with a tag on a gitlab with CI active.

It should reproduce the problem.

Environment:

https://framagit.org/1000i100/g1lien/-/blob/master/.gitlab-ci.yml#L5
https://framagit.org/1000i100/g1lien/-/jobs/1072052#L17

• OS: Docker in gitlab with image: node:current
• Node: v14.7.0
• NPM: 6.14.7

[maxsmaleha]

Same error.

Last release 30.07 was successful. But since 11.08 I get this error when publish:
2020-08-13T09:56:54.1669946Z 18 http fetch PUT 404 https://registry.npmjs.org/@aurigma%2fui-framework 5611ms
2020-08-13T09:56:54.1670114Z 19 verbose stack Error: 404 Not Found - PUT https://registry.npmjs.org/@aurigma%2fui-framework - Not found

[tschaub]

I was trying to npm publish from a new machine and got the same unexpected 404. In my case it was solved by an npm login. I understand that a 401 could "leak" the presence of a private package, but I would think the CLI would first check to see whether I was authenticated first and respond with a more appropriate error.

Here is the relevant portion of the log when I tried to npm publish before npm login:

19 verbose stack Error: 404 Not Found - PUT https://registry.npmjs.org/mock-fs - Not found
19 verbose stack     at /Users/tschaub/.nvm/versions/node/v14.8.0/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:117:15
19 verbose stack     at processTicksAndRejections (internal/process/task_queues.js:93:5)
20 verbose statusCode 404
21 verbose pkgid mock-fs@4.13.0
22 verbose cwd /Users/tschaub/projects/mock-fs
23 verbose Darwin 19.6.0
24 verbose argv "/Users/tschaub/.nvm/versions/node/v14.8.0/bin/node" "/Users/tschaub/.nvm/versions/node/v14.8.0/bin/npm" "publish"
25 verbose node v14.8.0
26 verbose npm  v6.14.8
27 error code E404
28 error 404 Not Found - PUT https://registry.npmjs.org/mock-fs - Not found
29 error 404
30 error 404 'mock-fs@4.13.0' is not in the npm registry.
31 error 404 You should bug the author to publish it (or use the name yourself!)
32 error 404 Note that you can also install from a
33 error 404 tarball, folder, http url, or git url.
34 verbose exit [ 1, true ]

[maxsmaleha]

Yeah, npm login helps. A few days ago I discovered this too. But still it is not clear why I had to re-authorize
Npm should improve their error messages.

[burtonator]

Hitting this issue too. Honestly I've had so many bugs / problems with npm and registries. It's a comedy of errors.

Right now I just did a login, removed all tokens, created a new one. Updated my .npmrc then did an npm ping

which works properly.

Then an npm publish gives me "not found".

I have to remove the .npmrc then do an npm login and then it works.

The problem is that this completely breaks our release process and we can't use a CI system for our releases.

NPM... you need to take these issues seriously. They really negatively impact your brand. Bugs like this and SO many in one area shouldn't exist. Either remove the features or fix them.

[ljharb]

Have you tried with npm 7?

[burtonator]

@ljharb I haven't ... could try that. was being lazy on upgrading 👍

[Maxim-Mazurok]

Also getting this error in my CI, I'm using token for login and trying to publish package which was previously published, still got 404: CI run
Sometimes I get 503, but that's probably just because I try to publish too many of them at a time... CI run 503
Related issue: Maxim-Mazurok/google-api-typings-generator#418

Using npm v6.14.10

[1000i100]

i fixed my problem by adding tags pattern v* as protected in gitlab. My CI silently failed to acces the token because it was only available on protected branch and tags and i had no protected tags and no publish task on protected branch.

[1nVitr0]

I'm experiencing the same problem recently. First I thought I messed up my CI, but when I manually login to github packages using my personal access token I get the same error.

My process:

$ npm login --registry=https://npm.pkg.github.com/
  > Username: 1nvitr0
  > Password: my token with write:package access
  > Email: (this IS public) my email
  > Logged in as 1nvitr0 on https://npm.pkg.github.com/.

When i run npm publish I receive a 404 error:

npm ERR! code E404
npm ERR! 404 Not Found - PUT https://npm.pkg.github.com/package-name The expected resource was not found.
npm ERR! 404 
npm ERR! 404  'package-name@version' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

UPDATE

Nevermind, I had an outdated repository URL and package name in my package.json. Updating that fixed the Error. But getting a 404 most definitely did not make that clear in any way.