npm / registry-issue-archive

An archive of the old npm registry issue tracker
https://npm.community
249 stars 47 forks source link

Unable to unpublish scoped package #316

Closed katagatame closed 6 years ago

katagatame commented 6 years ago

I've recently authored this package and am no longer able to access it.

The name and version within the package.json are

"name": "@kata-codes/yamdbf-log-to-file",
"version": "1.2.5"

I've tried to unpublish it:

npm unpublish --force
npm WARN using --force I sure hope you know what you are doing.
npm ERR! code E404
npm ERR! 404 Not found : 12-e33ab6bf4f41f894b6bc3b00d86890e9
npm ERR! 404
npm ERR! 404  '12-e33ab6bf4f41f894b6bc3b00d86890e9' 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.

I've tried to publish over it:

npm publish
npm ERR! publish Failed PUT 404
npm ERR! code E404
npm ERR! 404 Not found : @kata-codes/yamdbf-log-to-file
npm ERR! 404
npm ERR! 404  '@kata-codes/yamdbf-log-to-file' 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.

The package appears to not be in the registry: https://registry.npmjs.com/@kata-codes/yamdbf-log-to-file

Yet I am still able to install it via npm:

npm i --save @kata-codes/yamdbf-log-to-file

+ @kata-codes/yamdbf-log-to-file@1.2.5

Any help would be much appreciated!

katagatame commented 6 years ago

npm support has unpubbed this package.