npm publish has resulted in error "You need to authorize this machine using `npm adduser`" about how-to-npm

[AnandWalvekar]

It go resolved!!!

1. Switch to Login module (by typing "how-to-npm" on command line)
2. Type "npm adduser" to login
3. Type "npm whoami" to confirm if logged in
4. Switch back to the package at which you are getting error(my case it was Publish Again)
5. Type "npm publish"
6. Done

[petermetz]

My issue was that I had the publishConfig object specified in package.json which defined an invalid URL (some private registry).
Had to set it up like this:

  "publishConfig": {
    "registry": "https://registry.npmjs.org/"
  },

[renatoathaydes]

Does not work!

npm adduser
Username: xxxxxx
Password:
Email: (this IS public) [email protected]
Logged in as xxxxx on https://registry.npmjs.org/.
➜  lib1 npm publish
npm ERR! code ENEEDAUTH
npm ERR! need auth auth required for publishing
npm ERR! need auth You need to authorize this machine using `npm adduser`

[devhammer]

@AnandWalvekar That workaround didn't work for me. Still fails to publish, even when npm whomi correctly returns my username.

Getting the following output:

npm ERR! publish Failed PUT 404
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "node" "C:\\Users\\USERNAME\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "publish"
npm ERR! node v0.12.5
npm ERR! npm  v2.13.3
npm ERR! code E404

npm ERR! 404 missing : @myUser/how-to-npm
npm ERR! 404
npm ERR! 404 '@myUser/how-to-npm' 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!     C:\Users\USERNAME\Documents\node_code\nodeschool.io\how-to-npm\npm-debug.log

[Carnia]

My issue was that I had the publishConfig object specified in package.json which defined an invalid URL (some private registry).
Had to set it up like this:

  "publishConfig": {
    "registry": "https://registry.npmjs.org/"
  },

yes, when i delete publishConfig in package.json，I can publish it normally。

[JMuhire]

In my ci script, I have resolved this issue using a _auth token and setting up the user email like this :

npm config set _auth $NPM_REGISTRY_TOKEN && npm config set registry $NPM_REGISTRY_URL && npm config set always-auth=true && npm config set [email protected]

[yordis]

I keep getting the same error even when I successfully login. npm whoam give me the correct user but it keep failing no matter what.

[alundiak]

@renatoathaydes

1. What OS u have?
2. what is ur .npmrc content or
3. what is output of npm config list?

I see, you have https://registry.npmjs.org/ as registry, so I assume npm get registry will show it. have you tried to change to http://registry.npmjs.org/ (http).

4. strict-ssl = false set?
5. Are u under/behind the some proxy/vpn?

[swestcott]

Ditto, same software versions and same error.

[meppsilon]

I'm running into this error as well. Any suggestions on how to bypass it?

[smirciat]

Same issue here. It sounds like @alabebop has a workaround, but I am too new to this environment to understand it. Is any further guidance available?

[jmanuel1]

Getting same error as @devhammer, with node v0.10.35 on Windows 10.

[quangnd]

AnandWalvekar's solution worked with me!

[davis3792]

The work around fixed it for me as well. Wasted a bunch of time getting there though.

[su6a12]

Solution worked for me as well, thanks @AnandWalvekar

[seonixx]

Workaround worked for me. Cheers @AnandWalvekar

[bennythejudge]

@AnandWalvekar thanks a lot it worked but I had to bump the version.
Could a skip be provided for this step?

[jondcoleman]

Also had this error and workaround worked for me.

[aclbros]

Workaround worked for me. Cheers @AnandWalvekar

[ashleygwilliams]

closing in favor of #46. i believe the windows problem is already doc'd in #37

[agungsantoso]

AnandWalvekar's solution worked with me!

[sawant]

I have documented the issue and solution here #8 (comment) .

[piyushdubey]

@AnandWalvekar's solution worked for me as well!

[lpix]

@AnandWalvekar's solution worked for me! I suggest adding this as a tip in the module in case someone has the same issue

[sudoVlad]

@AnandWalvekar Thanks for the solution

[swheatley]

I had to go through the steps a few times but the work around for the solution mentioned above does work :)

[sergiomgaspar]

@AnandWalvekar thx for the WA.. worked like a charm :)

[alundiak]

@AnandWalvekar solution works for me locally. but At the moment I can't figure out why the same flow doesn't work on Jenkins.
If someone has ideas, I will very thankful.

This is cut from my custom .npmrc file created by Jenkins.

; userconfig /home/builder/.jenkins/jobs/FDD test - simple project/workspace@tmp/config3550090785588839693tmp
always-auth = true
registry = "https://my-server.com:8443/repository/my-hosted-npm"
strict-ssl = false

always-auth = true means, that I provided NPM user credentials on jenkins level, and I expected Jenkins pass/substitute creds during npm publish but I can't get why it doens't work..

[renatoathaydes]

OS: Linux renato 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

//registry.npmjs.org/:_authToken=cef314xxxxxxx
init.author.name=Renato Athaydes
init.author.email=renatoathaydes@xxxx

➜  npm config list
; cli configs
metrics-registry = "https://registry.npmjs.org/"
scope = ""
user-agent = "npm/5.6.0 node/v9.4.0 linux x64"

; userconfig /home/renato/.npmrc
init.author.email = "renatoathaydes@xxxx"
init.author.name = "Renato Athaydes"

; node bin location = /home/renato/.nvm/versions/node/v9.4.0/bin/node
; cwd = /home/renato/programming/projects/node-lib-mismatch/lib3
; HOME = /home/renato
; "npm config ls -l" to show all defaults.

I am at home, no proxies. No strict-ssl = false that I can see. And I would prefer to not use http.

[zrubing]

npm whoami is correct
I use sudo npm publish is failure,when i switch back to normal user then it worked

[Bittttter]

I just delete currentdir/.npmrc and then use nrm use to switch npm registry. And It works.

[geoidesic]

@Bittttter nrm use is not a thing. ?

[TylerSustare]

I had to go pro, publish the package, make the package public, and open a ticket to get my money back. It was super stupid.

[zuenir]

It go resolved!!!

1. Switch to Login module (by typing "how-to-npm" on command line)
2. Type "npm adduser" to login
3. Type "npm whoami" to confirm if logged in
4. Switch back to the package at which you are getting error(my case it was Publish Again)
5. Type "npm publish"
6. Done

Thank you, it helped to solve my problem

[sinawic]

In my ci script, I have resolved this issue using a _auth token and setting up the user email like this :

npm config set _auth $NPM_REGISTRY_TOKEN && npm config set registry $NPM_REGISTRY_URL && npm config set always-auth=true && npm config set [email protected]

@JMuhire
its 2024 and I wanna thank u for this!

i just added
registry=
_authToken=
to the .npmrc file and it workeddd