How to unpublish an npm package after 72 hours

[sharadraju]

HI,
We would like to replace our current package version due to a packaging issue, yet keep the same version number.
I am not able to unpublish the package because of 72-hour lapse.
Can anyone from the npm repository maintenance team help

[ebndev]

Hi @sharadraju, thanks for being a part of the GitHub Community!

According to the npm Unpublish policy: if your package was published more than 72 hours ago, you can unpublish it if it meets the criteria listed. However, it doesn't look like it would be possible to keep the same version number.

If you're worried about users downloading that old version, you can use npm deprecate instead to point them to the correct version.

Best of luck!

[sharadraju]

Hi @ebndev Thanks for the response. I tried unpublishing that specific version, but could not do so because of this criteria.
However I would like to unpublish a specific version of the npm package or not allow users to download it.

Can you please help us with that?

[ebndev]

Hey @sharadraju!

The doc also has a section on using npm deprecate if your version doesn't meet the criteria. Users will be able to install it, however will get a clear warning that it is deprecated and that version shouldn't be used.

If that doesn't work for you, you can try to directly contact support to ask if they can remove your package.

[TinaYTR]

Hi @ebndev, I also have the same problem to unpublish a package. I have tried to contact with support((https://www.npmjs.com/support), but get a wrong message when commit. What can I try for next? I want to unpublish the package as soon as possible.