Getting 404 when attempting to publish new package to NPM

Question

I just created a new package.

I'm now trying to publish it to NPM for the first time like this:

    ole@MKI:~/Sandbox/pli$ npm publish  --access public
    npm ERR! publish Failed PUT 404
    npm ERR! Linux 3.13.0-93-generic
    npm ERR! argv "/home/ole/.nvm/versions/v6.4.0/bin/node" "/home/ole/.nvm/versions/v6.4.0/bin/npm" "publish" "--access" "public"
    npm ERR! node v6.4.0
    npm ERR! npm  v3.10.3
    npm ERR! code E404

    npm ERR! 404 Not found : @supericium/pli
    npm ERR! 404 
    npm ERR! 404  '@supericium/pli' 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.

    npm ERR! Please include the following file with any support request:
    npm ERR!     /home/ole/Sandbox/pli/npm-debug.log

I tried updating both NodeJS and NPM to make sure that I have the latest version, which are:

ole@MKI:~/Sandbox/pli$ node --version
v6.4.0
ole@MKI:~/Sandbox/pli$ npm --version
3.10.3

Thoughts?

Yes, it makes no sense. Can't create a package because it doesn't exist. None of these answers solve the problem. — Steve, Sep 28 '21 at 01:53
@Distortum Try running `publish` in verbose mode - in a very frustrating way, in normal mode many issues end up as 404 while the real reason may be 403 because of a variety of issues. Usually running the verbose mode makes the issue apparent. — Oleg Valter is with Ukraine, Sep 28 '21 at 01:58

score 125 · Accepted Answer · edited Jan 19 '21 at 21:15

125

You need to have registered "supericium" (npm adduser) as a username at the registry and be logged in (npm login) to publish under that scope.

edited Jan 19 '21 at 21:15

Kevin Danikowski

4,620
6
41
75

answered Aug 24 '16 at 10:28

Stoffe

2,744
2
25
24

score 62 · Answer 2 · answered Sep 25 '20 at 07:24

62

It's solved by npm login in my case, the error message is misleading

answered Sep 25 '20 at 07:24

igonejack

2,366
20
29

It works... but when I published my package to **npm** their website stopped to work and shows me `error loading page` :))) – DenisKolodin Jan 16 '21 at 12:37
1

Sidenote: The problem isn't the client but that the npm registry sends 404. I've been told that when you e.g. use verdaccio as a proxy, it sends 401 if the login info is incorrect. Which makes the client show the expected "you need to log in" message. – AndyO May 09 '21 at 22:39
3

It doesn't work. – Steve Sep 28 '21 at 01:52

score 23 · Answer 3 · answered Dec 04 '18 at 02:03

23

Came across this same error, and my issue was that the package was somehow set to "Read" access only. So I have to go to the NPM and update the package to "Read/Write" access:

1.

2.

answered Dec 04 '18 at 02:03

Jee Mok

6,157
8
47
80

1

Spent so much time trying to fix it before I found this. Thanks ;) – Jacob Poul Richardt Apr 04 '19 at 16:04
1

NPM error messages are still confusing... Thanks for the hint, it solved my problem :) – Conaclos Jan 09 '22 at 17:06

score 13 · Answer 4 · answered Nov 13 '21 at 21:44

13

Nothing worked for me, except logging in again:

npm login

Hope this helps me or someone else in the future!

answered Nov 13 '21 at 21:44

Omar Dulaimi

846
10
30

score 9 · Answer 5 · answered Aug 10 '20 at 20:30

9

You could also get this error when you change your password to NPM but you do not logout/login via your CLI. Using npm logout and then npm login worked for me.

answered Aug 10 '20 at 20:30

Klemen

91
1
1

Ugh... This was it for me. There is nothing telling you you're not logged in. – Will Strohl Sep 15 '20 at 01:43

score 6 · Answer 6 · answered Nov 22 '20 at 17:06

6

in my case I had to verify the email address. even when npm whoami was telling me I was logged in fine.

answered Nov 22 '20 at 17:06

dcsan

11,333
15
77
118

How did you verify the email address? By executing `npm config ls` or something different? – Derek Hubbard Jun 04 '21 at 23:01

score 4 · Answer 7 · answered Aug 01 '20 at 10:21

4

In my case, I was missing the repository field in the package.json of my new package that I was trying to publish.

"repository": "git://github.com/your-org/your-repo-name.git"

https://docs.npmjs.com/files/package.json#repository

answered Aug 01 '20 at 10:21

Janno Teelem

324
2
6

score 4 · Answer 8 · answered Jan 29 '21 at 14:14

In my case, I got this message because the token that I was using had been revoked. I fixed it by:

Generating a new access token in my npm account.
Modifying the line: export NPM_TOKEN="<token>" in my .zshrc (or .bashrc) file
Entering source ~/.zshrc in the terminal.

score 4 · Answer 9 · answered Aug 04 '21 at 07:26

4

I just logged in to npm by using npm adduser command and it worked fine.

answered Aug 04 '21 at 07:26

ASANIAN

372
2
8

1

Whoa! This was the answer for me. Despite being authenticated via command line I had to re-add my user and retry the publish. Really bad CLI experience on that one. – Ben Racicot Oct 26 '21 at 13:54

score 3 · Answer 10 · answered Jan 09 '23 at 07:25

This error appeared for me in two cases:

When I wasn't logged in. You can check whether you are logged in or not by npm whoami, then if not logged in npm login.
When I didn't have right to publish to the repository. In this case make sure you are added to the organization which owns the repo.

score 1 · Answer 11 · answered Dec 20 '18 at 07:05

in my case i noticed that my npm account username in npm website is different than my npm normal user name. When i try to publish in console by login with normal username gave me this error.

publish Failed PUT 404 npm ERR! code E404 npm ERR! 404 User not found

But after login to console with account name it has published successfully

Greg Wozniak · Answer 12 · 2019-03-14T10:07:40.467

Once you successfully publish the package you may experience when you try to npm install:

npm ERR! code E404
npm ERR! 404 Not Found: @xxx/yyy@latest

or something similar, regardless if you npm publish was successful. In this case make sure your {main: 'file.js'} in packages.json is there.

Ideally, you can call it index.js if you wish to leech directly from the package so you don't get things like import * from '@xxx/yyy/file'.

score 1 · Answer 13 · answered Nov 18 '21 at 22:01

1

In my case, I believe I enabled 2FA on npmjs.com so the publish token used in CD didn't work (should have thrown 401, but got 404).

Generating a new automation token on npmjs.com and updating the secret on my CD (GitHub actions) solved it.

answered Nov 18 '21 at 22:01

Izhaki

23,372
9
69
107

score 0 · Answer 14 · answered May 01 '20 at 15:17

0

I encountered the same problem but I successfully resolved it by uninstalling the LTS version, then installing Current version along with yarn.

answered May 01 '20 at 15:17

Nicodemus Ngufuli

81
6

score 0 · Answer 15 · edited Jun 16 '21 at 17:14

Just adding my two cents to the possible solutions

I was getting this error in a CI workflow, so no interactive login or things related. Existing packages were working correctly, but adding a new one wasn't, I was getting a 404. I realized that it should be something related to the new package itself, not the CI environment, and it was.

The new package was missing two fields on its package.json, the repository and publishConfig fields.

Adding these two fields, it worked correctly (note that repository field is used in its expanded form, with the directory property)

"repository": {
  "type": "git",
  "url": "ssh://git@github.com/__user__/__repo-name__.git",
  "directory": "packages/__new-package-name__"
},
"publishConfig": {
  "registry": "https://npm.pkg.github.com/"
}

score 0 · Answer 16 · answered Jul 28 '22 at 12:10

0

For me the fix seemed to be making a new "team" in the organisation and assigning myself and my package to this.

My guess is that my NPM organisation requires users to have 2FA on and two users assigned to the 'developers' group didn't have this on.

answered Jul 28 '22 at 12:10

13twelve

121
5

score 0 · Answer 17 · answered Jun 29 '23 at 11:06

0

publish to npm.pkg.github.com, this error stems from incorrect 'name' in package.json. name should be aligned to github scope. so : @

then you can go ahead and publish.

answered Jun 29 '23 at 11:06

RG-josf

1

score -1 · Answer 18 · answered Feb 02 '22 at 12:50

In my case the problem was completely different.

I had to replace:

npm publish FOLDERNAME

with simply:

cd FOLDERNAME && npm publish

In my case I also had to manually specify the path of .npmrc using the --userconfig parameter:

cd myapp && npm publish -ddd --userconfig ../.npmrc

score -2 · Answer 19 · answered Jun 26 '20 at 23:40

-2

In my case i accidentally typed https://registry.npmjs.org instead of https://registry.npmjs.com (.org vs .com)

answered Jun 26 '20 at 23:40

Skylar Brown

3,234
2
14
7

1

The default in the docs lists `.org` as the correct URL - https://docs.npmjs.com/cli/v7/using-npm/config#registry – jthegedus Jul 21 '21 at 01:05

score -3 · Answer 20 · answered Jul 13 '22 at 01:52

-3

In my case, I had a typo when passing the otp param:

// Wrong:
npm publish --access public --opt 123456

// Correct:
npm publish --access public --otp 123456

answered Jul 13 '22 at 01:52

Matthew

2,871
5
34
59

Getting 404 when attempting to publish new package to NPM

20 Answers20

Linked