Cli: [BUG] npm publish claims my package does not exist

Created on 15 Jun 2020 · 8Comments · Source: npm/cli

What / Why

i'm trying to run npm publish to release a new version of my package

When

when i run npm publish (today)

Where

@cloudflare/wrangler

How

Current Behavior

run npm publish from project root

$ npm publish
npm notice 
npm notice 📦  @cloudflare/[email protected]
npm notice === Tarball Contents === 
npm notice 1.3kB binary.js            
npm notice 71B   install-wrangler.js  
npm notice 63B   run-wrangler.js      
npm notice 75B   uninstall-wrangler.js
npm notice 9.4kB npm-shrinkwrap.json  
npm notice 1.0kB package.json         
npm notice 6.6kB README.md            
npm notice === Tarball Details === 
npm notice name:          @cloudflare/wrangler                    
npm notice version:       1.10.0                                  
npm notice package size:  6.8 kB                                  
npm notice unpacked size: 18.5 kB                                 
npm notice shasum:        e67f7a41fdac9f30130bad380f545b796e10a5e1
npm notice integrity:     sha512-CFu2S+5kewuCD[...]28Jgmzmcs1T3A==
npm notice total files:   7                                       
npm notice 
npm ERR! code E404
npm ERR! 404 Not Found - PUT https://registry.npmjs.org/@cloudflare%2fwrangler - Not found
npm ERR! 404 
npm ERR! 404  '@cloudflare/[email protected]' 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! A complete log of this run can be found in:
npm ERR!     /Users/averyharnish/.npm/_logs/2020-06-15T20_07_51_611Z-debug.log

Steps to Reproduce

not sure - i can reproduce every time i run wrangler publish on my package but not sure how to reproduce w/o same permissions as me

Expected Behavior

successfully publish latest version

Who

@averyharnish

Source

EverlastingBugstopper

👍6

All 8 comments

Having this issue as well

RettBehrens on 15 Jun 2020

👀3

having the same problem

guisimo on 16 Jun 2020

npm status page says this is fixed, so im going to close this issue.

EverlastingBugstopper on 18 Jun 2020

Having this problem today
https://gitlab.com/Nexxkinn/vercel-deno/-/jobs/603441070

Nexxkinn on 19 Jun 2020

Also experiencing the issue

JaegerMa on 19 Jun 2020

I hadn't set the authtoken. Working now again.
However, I think it's weird that a 404 and the unambiguous message that the package doesn't exist is sent when no authtoken is passed.

JaegerMa on 19 Jun 2020

It's working now again.
you can close this issue.

Nexxkinn on 20 Jun 2020

I believe i'm still experiencing this; on both node 10 and 12 using nvm. Do i need to update node or npm to get it to work?

npm notice === Tarball Details === 
npm notice name:          publiclab-editor                        
npm notice version:       2.1.0                                   
npm notice package size:  669.0 kB                                
npm notice unpacked size: 1.4 MB                                  
npm notice shasum:        7c26176263ce3dc58204bbf6ebd3de2970c6a624
npm notice integrity:     sha512-6AZsTSzuyl4lO[...]bhhsU2vnbX7ZA==
npm notice total files:   67                                      
npm notice 
npm ERR! code E404
npm ERR! 404 Not Found - PUT https://registry.npmjs.org/publiclab-editor - Not found
npm ERR! 404 
npm ERR! 404  '[email protected]' 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.