尝试向 NPM 发布新包时获取404

我刚创建了一个 新包裹。

我现在正试图像这样第一次将它发布到 NPM:

    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

我尝试更新 NodeJS 和 NPM，以确保我有最新的版本，它们是:

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

有什么想法吗？

94730 次浏览
小开
最佳答案

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.

小开

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

小开

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

小开

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

小开

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

小开

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

小开

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

小开

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.

小开

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

小开

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

小开

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.
小开

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/"
}
小开

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

小开

Nothing worked for me, except logging in again:

npm login

Hope this helps me or someone else in the future!

小开

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.

小开

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
小开

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
小开

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.


提交答案