npm-unpublish should have some type of warning when unpublishing package.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 777
- Forks
- 267
- PR merge metrics
- No merged PRs in 30d
Description
Hi✌️.
Okay wait listen i am sure there are reasons for doing the waiting period but i think it make user experience a little better if we have warning like that i am just publishing some stupid tailwind scrollbar package but what if someone did that have more users being depended on them.
npm-unpublish should have some type of warning when unpublishing the version(like for example it was the last remaining version of the package or in my case the first version).
If you are republishing the version of the package it says to wait to 24 hours until you republish it , i think we should have warning mentioning the same when using the command npm-unpublish on our package.
It would be nice if -
npm unpublish [<@scope>/]<pkg>@<version>
-Hey woaah wait are you sure because you have to wait for 24 hours?
Warning: Unpublished packages may not be republished for 24 hours.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the npm unpublish command and its existing confirmation behavior. Define how the warning should apply when removing a version or the package's only version, including the 24-hour republish restriction. Done means the command clearly warns users before unpublishing and tests cover the proposed cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100