Getting 404 when attempting to publish new package to NPM

73
votes

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?

14
node.jsnpmnpm-publish
Yes, it makes no sense. Can't create a package because it doesn't exist. None of these answers solve the problem. – Distortum
@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

14 Answers

83
votes

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.

44
votes

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

17
votes

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.

enter image description here

2.

enter image description here

9
votes

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.

4
votes

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

2
votes

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

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

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

1
votes

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'.

1
votes

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

0
votes

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

0
votes

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

0
votes

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://[email protected]/__user__/__repo-name__.git",
  "directory": "packages/__new-package-name__"
},
"publishConfig": {
  "registry": "https://npm.pkg.github.com/"
}
0
votes

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

-8
votes

If you publish from an ubuntu envinroment, first authenticate with npm login then after just do

sudo npm publish