Closed prettydiff closed 2 years ago
It would be helpful if the log indicated the cause for the 403.
Closing: this looks to be an issue with the registry which is outside the scope of this repo. For registry support please go to npmjs.com/support. If you believe this is a bug with the cli, please provide further clarifying details.
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
Attempting to publish an existing package that I own and already exists on the registry. Version on the registry is 0.2.10 and am attempting to publish version 0.2.13.
Expected Behavior
New version published to registry.
Steps To Reproduce
npm publish
Environment
prefix = "C:\Users\austincheney\AppData\Roaming\npm"
; "user" config from C:\Users\austincheney.npmrc
//registry.npmjs.org/:_authToken = (protected)
; node bin location = C:\Program Files\nodejs\node.exe ; node version = v18.6.0 ; npm local prefix = C:\Users\austincheney\share-file-systems ; npm version = 8.15.0 ; cwd = C:\Users\austincheney\share-file-systems ; HOME = C:\Users\austincheney ; Run
npm config ls -l
to show all defaults.