Unpublish broken versions on npm
See original GitHub issueThere are a few versions on the npm package that don’t really make sense:
npm view prismjs
{ "name": "prismjs",
"dist-tags": { "latest": "1.3.0" },
"versions": [ "0.0.1", "1.1.0", "1.2.0", "1.3.0", "9000.0.1" ],
"time":
{
"9000.0.1": "2015-05-12T23:54:40.643Z",
"9000.0.2": "2015-05-12T23:56:14.033Z",
"0.0.1": "2015-05-13T00:37:38.541Z",
"1.1.0": "2015-10-06T00:03:04.995Z",
"1.2.0": "2015-10-07T17:35:20.776Z",
"1.3.0": "2015-10-27T02:35:27.738Z" }
}
The following should remove the versions…
npm unpublish prismjs@9000.0.1
npm unpublish prismjs@9000.0.2
Issue Analytics
- State:
- Created 8 years ago
- Reactions:2
- Comments:13 (10 by maintainers)
Top Results From Across the Web
npm-unpublish
Even if you unpublish a package version, that specific name and version combination can never be reused. In order to publish the package...
Read more >"publish --force" and "unpublish VERSION" seem to be broken ...
1. First I publish the package in an empty registry. /verdaccio_s3_db.json is updated correctly · 2. I try to unpublish the package. NPM...
Read more >unpublish | npm Documentation
If no version is specified, or if all versions are removed then the root package entry is removed from the registry entirely. Even...
Read more >npm Blog Archive: changes to npm's unpublish policy
If the version is less than 24 hours old, you can unpublish it. The package will be completely removed from the registry.
Read more >How do you delete all previous versions of a published npm ...
With the default registry (registry.npmjs.org), unpublish is only allowed with versions published in the last 72 hours. If you are trying to ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This is being handled by npm support and should be fixed shortly.
Seems to have worked? Although I still see the version here: https://www.npmjs.com/package/prismjs
Dunno if that’s a caching thing; will recheck in a bit.